[Now to upgrade 1.4 container to next-release?]

Thank you.

 

[Now to upgrade 1.4 container to next-release?]

On 1/11/2024 at 3:18 AM, grouche said:

Hi @bpaddock  people have successfully upgraded but it is unsupported.  Please back up your system before proceeding!

https://www.funtoo.org/Upgrade_Instructions/Next

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?

[Now to upgrade 1.4 container to next-release?]

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?

 

[ego fails after 1.4 upgrade has simple fix]

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.
 

[Ego index error, Meta-repo RdOnly, bad profile]

 

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

Quote

Sync successful and kits in alignment! :)

Updating /etc/portage/repos.conf...

Updating profiles at /etc/portage/make.profile/parent...

Updating non-funtoo repositories...

ERROR: Ego encountered an unexpected error: ImportError

 

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.

 

Quote

eix-sync
warning: ignoring parent gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit of file /etc/portage/make.profile/parent
warning: ignoring parent gentoo:funtoo/1.0/linux-gnu/build/current of file /etc/portage/make.profile/parent
warning: ignoring parent gentoo:funtoo/1.0/linux-gnu/flavor/core of file /etc/portage/make.profile/parent
 * Running ego sync
WARNING: Meta-repo is read-only -- running in config-only mode.
Updating /etc/portage/repos.conf...
ERROR: Ego encountered an unexpected error: IndexError
ERROR: Full traceback written to /tmp/ego-traceback-26322.txt.

This is the ego traceback:

 

Quote

                
  File "/usr/share/ego/python/ego/profile.py", line 420, in __init__
    self.reload()
  File "/usr/share/ego/python/ego/profile.py", line 434, in reload
    self.profile_hier = self._recurse(parent_lines=parent_lines)
  File "/usr/share/ego/python/ego/profile.py", line 617, in _recurse
    new_children[spec_obj] = self._recurse(spec_obj, _parent=spec_obj, repo_nam\
e=spec_obj.repo_name)
  File "/usr/share/ego/python/ego/profile.py", line 606, in _recurse
    res_path = profile_path.resolved_path if profile_path is not None else self\
.root_parent_dir
  File "/usr/share/ego/python/ego/profile.py", line 337, in resolved_path
    if self.spec_str[0] == ":":
IndexError: string index out of range

 

Quote

eselect python list
Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7
  [3]   python3.4

 

[ZFS Install Problems with current portage]

11 hours ago, Oleg Vinichenko said:

the wiki is open, please, correct.

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.

[ZFS Install Problems with current portage]

11 hours ago, Oleg Vinichenko said:

the wiki is open, please, correct.

the kernel update has to be performed manually with recreation of new initramfs with --zfs argument. This applies for both: kernel update or zfs tools update. This is reflected in wiki. Please, post what exact stage3 you used (with date of stage), so that's it's possible to check what ego version included.

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.
 

[ZFS Install Problems with current portage]

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.