Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 516518 - emerge and equery print "No supported implementations match python_gen_usedep patterns: python2_6" errors after sync
Summary: emerge and equery print "No supported implementations match python_gen_usedep...
Status: RESOLVED DUPLICATE of bug 516520
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-06 13:58 UTC by Coacher
Modified: 2014-07-06 16:15 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (info,5.05 KB, text/plain)
2014-07-06 14:00 UTC, Coacher
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Coacher 2014-07-06 13:58:55 UTC
Hello.

Today I resynced my portage tree as usual with `emerge --sync`. Now my emerge and gentoolkit tools spit out errors in console.

Here are some examples:

$ equery d python-unittest2
 * These packages depend on python-unittest2:
 * ERROR: virtual/python-argparse-1::gentoo failed (depend phase):
 *   No supported implementations match python_gen_usedep patterns: python2_6
 *
 * Call stack:
 *                  ebuild.sh, line 545:  Called source '/var/portage/virtual/python-argparse/python-argparse-1.ebuild'
 *   python-argparse-1.ebuild, line  19:  Called python_gen_cond_dep 'dev-python/argparse[${PYTHON_USEDEP}]' 'python2_6'
 *           python-r1.eclass, line 373:  Called python_gen_usedep 'python2_6'
 *           python-r1.eclass, line 293:  Called die
 * The specific snippet of code:
 *      [[ ${matches[@]} ]] || die "No supported implementations match python_gen_usedep patterns: ${@}"
 *
 * If you need support, post the output of `emerge --info '=virtual/python-argparse-1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=virtual/python-argparse-1::gentoo'`.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/virtual/python-argparse-1/work/python-argparse-1'
 * ERROR: virtual/python-unittest2-1-r2::gentoo failed (depend phase):
 *   No supported implementations match python_gen_usedep patterns: python2_6
 *
 * Call stack:
 *                      ebuild.sh, line 545:  Called source '/var/portage/virtual/python-unittest2/python-unittest2-1-r2.ebuild'
 *   python-unittest2-1-r2.ebuild, line  21:  Called python_gen_cond_dep 'dev-python/unittest2[${PYTHON_USEDEP}]' 'python2_6'
 *               python-r1.eclass, line 373:  Called python_gen_usedep 'python2_6'
 *               python-r1.eclass, line 293:  Called die
 * The specific snippet of code:
 *      [[ ${matches[@]} ]] || die "No supported implementations match python_gen_usedep patterns: ${@}"
 *
 * If you need support, post the output of `emerge --info '=virtual/python-unittest2-1-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=virtual/python-unittest2-1-r2::gentoo'`.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/virtual/python-unittest2-1-r2/work/python-unittest2-1'


# emerge -pvuDN world

These are the packages that would be merged, in order:

Calculating dependencies | * ERROR: virtual/python-unittest2-1-r2::gentoo failed (depend phase):
 *   No supported implementations match python_gen_usedep patterns: python2_6
 *
 * Call stack:
 *                      ebuild.sh, line 545:  Called source '/var/portage/virtual/python-unittest2/python-unittest2-1-r2.ebuild'
 *   python-unittest2-1-r2.ebuild, line  21:  Called python_gen_cond_dep 'dev-python/unittest2[${PYTHON_USEDEP}]' 'python2_6'
 *               python-r1.eclass, line 373:  Called python_gen_usedep 'python2_6'
 *               python-r1.eclass, line 293:  Called die
 * The specific snippet of code:
 *      [[ ${matches[@]} ]] || die "No supported implementations match python_gen_usedep patterns: ${@}"
 *
 * If you need support, post the output of `emerge --info '=virtual/python-unittest2-1-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=virtual/python-unittest2-1-r2::gentoo'`.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/virtual/python-unittest2-1-r2/work/python-unittest2-1'
 | * ERROR: virtual/python-argparse-1::gentoo failed (depend phase):
 *   No supported implementations match python_gen_usedep patterns: python2_6
 *
 * Call stack:
 *                  ebuild.sh, line 545:  Called source '/var/portage/virtual/python-argparse/python-argparse-1.ebuild'
 *   python-argparse-1.ebuild, line  19:  Called python_gen_cond_dep 'dev-python/argparse[${PYTHON_USEDEP}]' 'python2_6'
 *           python-r1.eclass, line 373:  Called python_gen_usedep 'python2_6'
 *           python-r1.eclass, line 293:  Called die
 * The specific snippet of code:
 *      [[ ${matches[@]} ]] || die "No supported implementations match python_gen_usedep patterns: ${@}"
 *
 * If you need support, post the output of `emerge --info '=virtual/python-argparse-1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=virtual/python-argparse-1::gentoo'`.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/virtual/python-argparse-1/work/python-argparse-1'
... done!
[skipped list of packages to be updated here]


My guess it has something to do with recent CVS commits with this message:
Clean up obsolete dependencies on virtual/python-argparse and virtual/python-
unittest2 (those packages were only required for <=python-2.6).

However, I am worried if these errors happen because I haven't synced complete set of changes related to the mentioned cleanup or my system is really broken now?

Reproducible: Always
Comment 1 Coacher 2014-07-06 14:00:05 UTC
Created attachment 380302 [details]
emerge --info
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2014-07-06 16:11:17 UTC

*** This bug has been marked as a duplicate of bug 516510 ***
Comment 3 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2014-07-06 16:15:54 UTC
Sorry, wrong bug no.

*** This bug has been marked as a duplicate of bug 516520 ***