Summary: | [kde overlay] Repository 'kde' is implicitly using 'portage-1' profile format in its profiles/package.mask | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Till Schäfer <till2.schaefer> |
Component: | Profiles | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | kensington |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Till Schäfer
2018-05-30 12:24:38 UTC
This was introduced in https://gitweb.gentoo.org/proj/kde.git/log/?qt=range&q=16a1fe34aa0e4be7b9b55b523685e1de12a20ed1...9f28549817582741cebc1faa058d2621176d4094, but is legal because the profile uses EAPI 7. To avoid the warning, try upgrading portage. Here as well. sys-apps/portage-2.3.24-r1 is the last stable version. (In reply to Markus from comment #2) > Here as well. sys-apps/portage-2.3.24-r1 is the last stable version. That's fine, the overlay does not contain a single stable ebuild. So its not allowed to have a stable system with just some non-critical, selected parts unkeyworded? Nevertheless portage-2.3.40 was just marked stable. So the warning is gone. (In reply to Markus from comment #4) > So its not allowed to have a stable system with just some non-critical, > selected parts unkeyworded? Mixing arch with ~arch is one thing (and you get to keep the pieces), adding a development overlay is another. It is not unreasonable to expect the overlay be ahead of your stable tree offerings. |