-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
portage complains about ebuilds that come from mate kit have a non-existent category:
!!! 'mate-base/mate-panel' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-settings-daemon' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-menus' has a category that is not listed in /etc/portage/categories !!! 'mate-base/caja' has a category that is not listed in /etc/portage/categories !!! 'mate-base/libmatekbd' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-session-manager' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-control-center' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-desktop' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-common' has a category that is not listed in /etc/portage/categories !!! 'mate-base/mate-applets' has a category that is not listed in /etc/portage/categories
because of that, trying to emerge any new mate packages results in, e.g.
emerge: there are no ebuilds to satisfy ">=mate-base/mate-common-1.24".
manually creating a file in path /var/git/meta-repo/kits/mate-kit/profiles/categories with contents:
mate-base
makes the problem go away
