From: Jacques Montier <jmontier@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Python-3.9 and emerge problems
Date: Fri, 18 Jun 2021 16:26:18 +0200 [thread overview]
Message-ID: <CAHVEG0AJvvJyBv5eoDNMjvmBUbaaFzGyBG9y1hZuCxgDpK-2ng@mail.gmail.com> (raw)
In-Reply-To: <20210618150017.46cb817f@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
* <https://sites.google.com/site/jacquesfr35/>*
Le ven. 18 juin 2021 à 16:00, Neil Bothwick <neil@digimed.co.uk> a écrit :
> On Fri, 18 Jun 2021 09:54:09 -0400, John Covici wrote:
>
> > > Same problem with 3.0.20-r3 but then I found
> > > https://bugs.gentoo.org/796584, changing sets.conf got rid of the
> > > issue.
> >
> > hmmm, I don't have a file like that at all, what should be in that
> > file -- I don't even have a /usr/portage at all.
> >
> The system sets are in /usr/share/portage/config/sets, but they all had
> exclude-files where needed. The culprits were my user-defined sets in
> /etc/sets.conf. For example:
>
> [kernels]
> class = portage.sets.dbapi.OwnerSet
> world-candidate = False
> files = /usr/src
> exclude-files = ''
>
> Adding that last line stopped the breakage. This sort of change should
> have been accompanied by an einfo message at the very least, preferable a
> news item.
>
>
> --
> Neil Bothwick
>
> Top Oxymorons Number 43: Genuine imitation
>
Hello again,
Yes Neil, that did the trick ! 👍
Thanks a lot to all of you !
--
Jacques
[-- Attachment #2: Type: text/html, Size: 2193 bytes --]
next prev parent reply other threads:[~2021-06-18 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 9:46 [gentoo-user] Python-3.9 and emerge problems Jacques Montier
2021-06-18 11:20 ` John Covici
2021-06-18 11:45 ` Wols Lists
2021-06-18 12:07 ` Neil Bothwick
2021-06-18 13:11 ` Neil Bothwick
2021-06-18 13:54 ` John Covici
2021-06-18 14:00 ` Neil Bothwick
2021-06-18 14:26 ` Jacques Montier [this message]
2021-06-18 15:55 ` John Covici
2021-06-19 12:35 ` Jacques Montier
2021-06-18 13:26 ` John Covici
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=CAHVEG0AJvvJyBv5eoDNMjvmBUbaaFzGyBG9y1hZuCxgDpK-2ng@mail.gmail.com \
--to=jmontier@gmail.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