Page 1 of 1

[Solved] Portage broken from profile transition?

Posted: Mon Jun 01, 2020 0:46
by Duskmourn
It seems like Portage is just broken in several ways with the profile transition going on in Sabayon, is there a way to fix it? Anytime I try to emerge something I'm met with this

Code: Select all

[email protected] ~ $ sudo emerge --pretend games-action/ftb-launcher
/usr/lib64/python3.6/site-packages/portage/package/ebuild/_config/KeywordsManager.py:70: UserWarning: /etc/portage/package.keywords is deprecated, use /etc/portage/package.accept_keywords instead
  UserWarning)


!!! /etc/portage/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /usr/portage/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)


!!! Your current profile is invalid. If you have just changed your profile
!!! configuration, you should revert back to the previous configuration.
!!! Allowed actions are limited to --help, --info, --search, --sync, and
!!! --version.

Re: Portage broken from profile transition?

Posted: Mon Jun 01, 2020 4:28
by kris-kris
Maybe it will help? Check what profiles are available and choose the right one.

Code: Select all

eselect profile list
And select the profile number and enter in the command after set, e.g. 20

Code: Select all

eselect profile set 20

Re: Portage broken from profile transition?

Posted: Mon Jun 01, 2020 6:11
by sebaro
The repo make.profile still uses the old profile number:

/var/lib/entropy/client/database/amd64/sabayon-weekly/standard/amd64/5/make.profile
../usr/portage/profiles/default/linux/amd64/17.0/desktop
So on every equo update:
@@ /etc/make.profile: link differs. Updating.
Also pkconfig is broken.

Re: Portage broken from profile transition?

Posted: Thu Jun 04, 2020 10:58
by Duskmourn
So, is this just something I should wait for an update to fix, since pkg-config is just broken currently?

Re: Portage broken from profile transition?

Posted: Fri Jun 05, 2020 7:59
by sebaro
For profile, make sure /etc/portage/make.profile and /etc/make.profile are symlinks to the new profile.
Use the eselect commands above if they are not correct, also after "equo update".

For pkconfig, you don't have to do anything unless emerge fails with a pkgconfig error.
For me some packages fail to build (ffmpeg) and I did the following:

Code: Select all

USE="internal-glib" emerge dev-util/pkgconfig
emerge dev-libs/glib
emerge dev-util/pkgconfig