Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 720128 - gnome-base/libgnome-keyring uses python-any-r1 eclass incorrectly
Summary: gnome-base/libgnome-keyring uses python-any-r1 eclass incorrectly
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords: PullRequest
Depends on:
Blocks:
 
Reported: 2020-04-30 13:45 UTC by ta2002
Modified: 2020-04-30 15:53 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ta2002 2020-04-30 13:45:13 UTC
Wasted hours of my own time (and the time of others, as well).

Attempted to install gnome-base:libgnome-keyring-3.12.0-r1.

The compile died with the following message:

ERROR: setup
No Python implementation found for the build. This is usually
a bug in the ebuild. Please report it to bugs.gentoo.org
along with the build log.
ERROR: gnome-base/libgnome-keyring-3.12.0-r1::gentoo failed (setup phase):
  No supported Python implementation installed.

Call stack:
             ebuild.sh, line 125:  Called pkg_setup
             ebuild.sh, line 355:  Called python-any-r1_pkg_setup
  python-any-r1.eclass, line 361:  Called python_setup
  python-any-r1.eclass, line 349:  Called die
The specific snippet of code:
        die "No supported Python implementation installed."


It turns out that I still had 2.7.15 as my Python 2.7 version, and the portage tree has only 2.7.17-r2 and 2.7.18 (nobody in the forum suggested this as a possibility, so I will claim this doesn't fall into the "obvious error" category). I (and perhaps others in the future) would appreciate it if the error message simply said something like "Can't find Python 2.7.17-r2 or 2.7.18)." The 2.7.15 version most likely would have worked if portage allowed it, so I didn't consider that as the source of the problem, and I would have expected a reminder from portage to update Python 2.7 before attempting to compile this.
Comment 1 Mike Gilbert gentoo-dev 2020-04-30 14:06:20 UTC
Under normal circumstances, end-users should never see this error message. You only got that error because the libgnome-keyring ebuild uses the python-any-r1 eclass incorrectly.
Comment 2 Larry the Git Cow gentoo-dev 2020-04-30 15:53:17 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=62baf9140884a7191bce2b6eb2f48947bbbde195

commit 62baf9140884a7191bce2b6eb2f48947bbbde195
Author:     Mike Gilbert <floppym@gentoo.org>
AuthorDate: 2020-04-30 14:41:35 +0000
Commit:     Mike Gilbert <floppym@gentoo.org>
CommitDate: 2020-04-30 15:53:12 +0000

    gnome-base/libgnome-keyring: fix python-any-r1 eclass usage
    
    Closes: https://bugs.gentoo.org/708574
    Closes: https://bugs.gentoo.org/720128
    Signed-off-by: Mike Gilbert <floppym@gentoo.org>

 .../libgnome-keyring/libgnome-keyring-3.12.0-r1.ebuild      | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)