| Summary: | layman-2.4.2-r1 can't be emerged with default Python settings anymore | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nathan <ntf1> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This will be resolved as soon as bug 720934 is complete. It should have been stabled before the default transition, yes. *** This bug has been marked as a duplicate of bug 720934 *** |
The current stable layman can't be emerged any more with default Python settings - it requires obsolete Python 3.6: !!! The ebuild selected to satisfy "app-portage/layman" has unmet requirements. - app-portage/layman-2.4.2-r1::gentoo USE="cvs git mercurial subversion (-darcs) (-g-sorcery) -gpg -sqlite -squashfs -sync-plugin-portage -test" ABI_X86="(64)" PYTHON_TARGETS="-python3_6" The following REQUIRED_USE flag constraints are unsatisfied: python_targets_python3_6 The above constraints are a subset of the following complete expression: any-of ( python_targets_python3_6 ) IMHO stable ebuilds shouldn't behave like that.