Despite what multiple blog and wiki pages claim, it seems it's not as
simple as editing you gentoo.conf file. Do I need to wipe the contents
of /usr/portage and start with an emptry directory there?
On Tue, Oct 12, 2021 at 4:02 PM Grant Edwards <grant.b.edwards@gmail.com> wrote:
Despite what multiple blog and wiki pages claim, it seems it's not as
simple as editing you gentoo.conf file. Do I need to wipe the contents
of /usr/portage and start with an emptry directory there?
I believe so. I'd just rename the directory and let it get
re-created. Then you can delete the old one when you are confident
you don't need it.
no profile selected
On Tue, 2021-10-12 at 21:14 +0000, Grant Edwards wrote:
no profile selected
I'm surprised you had gotten this far without a profile selected.
Maybe you had previously selected one that was deprecated at some point
and removed from the list?
On Tue, Oct 12, 2021 at 9:01 PM Matt Connell <matthewdconnell@gmail.com> wrote:
On Tue, 2021-10-12 at 21:14 +0000, Grant Edwards wrote:
no profile selected
I'm surprised you had gotten this far without a profile selected.
Maybe you had previously selected one that was deprecated at some point
and removed from the list?
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.
Probably doesn't need to be a symlink, or in the repo, which is I'm
guessing how funtoo does mix-ins though I haven't actually checked
(just create a custom profile with the appropriate parent entries).
The Gentoo standard though is a symlink.
On Tue, 2021-10-12 at 21:14 +0000, Grant Edwards wrote:
no profile selected
I'm surprised you had gotten this far without a profile selected.
Maybe you had previously selected one that was deprecated at some point
and removed from the list?
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.
On 2021-10-13, Rich Freeman <rich0@gentoo.org> 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.
On Tue, Oct 12, 2021 at 9:22 PM Grant Edwards <grant.b.edwards@gmail.com> wrote:
On 2021-10-13, Rich Freeman <rich0@gentoo.org> 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.
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.
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.
The error messages may very well have been misleading though.
Portage is a bit infamous for misleading error messages.
Maybe you had previously selected one that was deprecated at some
point and removed from the list?
I assume that 'mv /usr/portage /usr/portage-old' cause my profile
selecttion to "go away".
You made the classic mistake of changing two things at once and then
not knowing which change caused the blow up!
You made the classic mistake of changing two things at once and then
not knowing which change caused the blow up!
Indeed. You'd think by now I'd have learned not to do that...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 62:11:04 |
Calls: | 6,488 |
Calls today: | 1 |
Files: | 12,096 |
Messages: | 5,274,518 |