From: John Covici <covici@ccs.covici.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] how to maintain and successfully compile inn
Date: Tue, 09 Feb 2021 06:58:10 -0500 [thread overview]
Message-ID: <m3r1lpmp0t.wl-covici@ccs.covici.com> (raw)
Hi. I see that inn is no longer in the tree and I have a local ebuild
for inn2.6.3, but it won't work because of the following line
PYTHON_COMPAT=( python2_7 )
The error I get is:
* ERROR: net-nntp/inn-2.6.3::local_ebuilds failed (depend phase):
* No supported implementation in PYTHON_COMPAT.
*
* Call stack:
* ebuild.sh, line 609: Called source
* '/usr/local/portage/net-nntp/inn/inn-2.6.3.ebuild'
* inn-2.6.3.ebuild, line 8: Called inherit
* 'autotools' 'eutils' 'multilib'
* 'python-single-r1' 'toolchain-funcs'
* ebuild.sh, line 314: Called __qa_source
* '/var/db/repos/gentoo/eclass/python-single-r1.eclass'
* ebuild.sh, line 112: Called source
* '/var/db/repos/gentoo/eclass/python-single-r1.eclass'
* python-single-r1.eclass, line 269: Called
* _python_single_set_globals
* python-single-r1.eclass, line 209: Called _python_set_impls
* python-utils-r1.eclass, line 156: Called die
* The specific snippet of code:
* die "No supported implementation in
* PYTHON_COMPAT."
I still have python 2.7 probably because of issues in building
chrome, so how do I fix things to keep portage happy and what should I
do going forward because I obviously don't want to depend on
python2.7 for actually running things.
I have mailman which I have to do something about as well, so I will
have to use their new ecosystem or switch to another mailing list
manager.
Thanks for any advice and thoughts on this subject.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
covici@ccs.covici.com
reply other threads:[~2021-02-09 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r1lpmp0t.wl-covici@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox