On 2021-10-13, Rich Freeman <[email protected]> wrote: > On Tue, Oct 12, 2021 at 9:22 PM Grant Edwards <[email protected]> > wrote: > >> On 2021-10-13, Rich Freeman <[email protected]> wrote: >> > >> > Profile selection is implemented as a symlink from >> > /etc/portage/make.profile. If you move your repository, then you need >> > to re-select the profile since the symlink will be broken. >> >> Indeed. And the failure that produces is not at all graceful. >> >> I spent a little time trying to figure out where in the Wiki or docs >> that the rsync -> git migration steps should be documented, but I >> didn't find anyplace that looked like the right home for that info. >> > > Moving from rsync to git probably doesn't require re-selecting the > profile. However, if you move the path of the repository itself then > that would require re-selecting the profile regardless of whether the > method of syncing is changed. > > I got the impression from your email that you moved the repository > when you switched.
Yes. I was in the old location /usr/portage, and I moved it to the new /var/db location. That's what broke the profile selection. > If you ONLY renamed the old one but kept the same exact path, then > after it pulled the new repo the profile should have remained > working as far as I am aware. I think that's correct. > If I'm understanding the situation, then the correct place to put > this in the wiki is in any section pertaining to moving the > repository (such as to /var/db or whatever). It wouldn't hurt to > make a note in any instructions for switching to git to be aware of > the requirement if the opportunity is taken to move the repository > at the same time. It is a pretty logical time to do this. That's certainly what I thought. :) > The error messages may very well have been misleading though. > Portage is a bit infamous for misleading error messages. There wasn't an error message at all. Just a Python stack trace becaus of an exception thrown because None doesn't have a startswith method. -- Grant
