on a fresh stage, gentoo ships an empty /usr/portage.
When a user unpacks said fresh stage and tries to sync, they are greeted with:
Atropos-XR usr # ls portage/
Atropos-XR usr # emerge --sync
!!! Section 'gentoo' in repos.conf refers to repository without repository name set in '/usr/portage/profiles/repo_name'
Unavailable repository 'gentoo' referenced by masters entry in '/var/lib/layman/pentoo/metadata/layout.conf'
!!! Unable to parse profile: '/etc/portage/make.profile'
!!! ParseError: Parent 'gentoo:default/linux/arm/13.0/armv7a' not found: '/var/lib/layman/pentoo/profiles/pentoo/default/linux/arm/parent'
!!! 'sys-apps/portage' has a category that is not listed in /etc/portage/categories
* An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* To update portage, run 'emerge --oneshot portage' now.
Not only is this a regression from 2.1 (which had no issues syncing from an empty /usr/portage) but the message is beyond useless as it gives entirely bad advice.
Please fix to properly sync from an empty /usr/portage without error.
sorry, not on a fresh stage, just on any system where /usr/portage was a bind mount (like all of the stages I create)
Portage 2.2.7 or and older version?
Current stable (2.2.1) - you can reproduce by simply deleting everything in /usr/portage - but leave /usr/portage there, and attempt to sync.
Looks like 2.2.7 fixes this, we really need to get that stabled.
This bug last appears in this commit:
5efeeb8fe8618e2ae8ecc6f774221746896774ee | dohtml: restore behavior noted in bug #425214
It disappears with this commit:
1e8c9a72279eeec615a3c25d3fef360888528b8b | Bug #484730: In sync mode, use repos.conf section name when repo_name file is missing.
This means it should be fixed in v2.2.5.
*** This bug has been marked as a duplicate of bug 484730 ***