Mailing List Archive

Python-3.9 and emerge problems
Hello all,

This morning :

#emerge --sync
#emerge --oneshot sys-apps/portage
#emerge -auvDN --with-bdeps=y --keep-going world

I get these errors :

Traceback (most recent call last):
File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
retval = emerge_main()
File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1319, in
emerge_main
return run_action(emerge_config)
File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 3392, in
run_action
retval = action_build(emerge_config, spinner=spinner)
File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 354, in
action_build
success, mydepgraph, favorites = backtrack_depgraph(
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 10005,
in backtrack_depgraph
return _backtrack_depgraph(settings, trees, myopts, myparams,
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 10043,
in _backtrack_depgraph
success, favorites = mydepgraph.select_files(myfiles)
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 4055,
in select_files
return self._select_files(args)
File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 4189,
in _select_files
set_atoms = root_config.setconfig.getSetAtoms(s)
File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py", line
271, in getSetAtoms
myatoms.update(self.getSetAtoms(s,
File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py", line
271, in getSetAtoms
myatoms.update(self.getSetAtoms(s,
File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py", line
260, in getSetAtoms
myatoms = myset.getAtoms()
File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line 58,
in getAtoms
self._load()
File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line 53,
in _load
self.load()
File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line 111,
in load
self._setAtoms(self.mapPathsToAtoms(self._files,
File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line 83,
in mapPathsToAtoms
for p in exclude_paths:
TypeError: 'NoneType' object is not iterable

And i can't do anything else...

I see that python-3.8 has gone away
# eselect python list
Available Python interpreters, in order of preference:
[1] python3.9

emerge --info file attached

I don't really know what to do.
Any idea ?

Thanks a lot in advance,

Regards,

*--*
*Jacques*
Re: Python-3.9 and emerge problems [ In reply to ]
On 18/06/21 10:46, Jacques Montier wrote:
> Hello all,
>
> This morning :
>
> #emerge --sync
> #emerge --oneshot sys-apps/portage
> #emerge -auvDN --with-bdeps=y --keep-going world

You can't try just updating python? When I tried to emerge portage it
blew up with loads of stuff about 3.8 and 3.9, so I just did an "emerge
-uDN python" and everything started working (well, emerge at least ... :-)

Cheers,
Wol
>
> I get these errors :
>
> Traceback (most recent call last):
> File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
> retval = emerge_main()
> File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1319, in
> emerge_main
> return run_action(emerge_config)
> File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 3392,
> in run_action
> retval = action_build(emerge_config, spinner=spinner)
> File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 354,
> in action_build
> success, mydepgraph, favorites = backtrack_depgraph(
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 10005, in backtrack_depgraph
> return _backtrack_depgraph(settings, trees, myopts, myparams,
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 10043, in _backtrack_depgraph
> success, favorites = mydepgraph.select_files(myfiles)
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 4055, in select_files
> return self._select_files(args)
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 4189, in _select_files
> set_atoms = root_config.setconfig.getSetAtoms(s)
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> line 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> line 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> line 260, in getSetAtoms
> myatoms = myset.getAtoms()
> File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line
> 58, in getAtoms
> self._load()
> File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line
> 53, in _load
> self.load()
> File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line
> 111, in load
> self._setAtoms(self.mapPathsToAtoms(self._files,
> File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line
> 83, in mapPathsToAtoms
> for p in exclude_paths:
> TypeError: 'NoneType' object is not iterable
>
> And i can't do anything else...
>
> I see that python-3.8 has gone away
> # eselect python list
> Available Python interpreters, in order of preference:
> [1] python3.9
>
> emerge --info file attached
>
> I don't really know what to do.
> Any idea ?
>
> Thanks a lot in advance,
>
> Regards,
>
> /--/
> /Jacques/
Re: Python-3.9 and emerge problems [ In reply to ]
On Fri, 18 Jun 2021 05:46:27 -0400,
Jacques Montier wrote:
>
> [1 <multipart/alternative (7bit)>]
> [1.1 <text/plain; UTF-8 (7bit)>]
> Hello all,
>
> This morning :
>
> #emerge --sync
> #emerge --oneshot sys-apps/portage
> #emerge -auvDN --with-bdeps=y --keep-going world
>
> I get these errors :
>
> Traceback (most recent call last):
> File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
> retval = emerge_main()
> File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1319, in
> emerge_main
> return run_action(emerge_config)
> File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 3392, in
> run_action
> retval = action_build(emerge_config, spinner=spinner)
> File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 354, in
> action_build
> success, mydepgraph, favorites = backtrack_depgraph(
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 10005,
> in backtrack_depgraph
> return _backtrack_depgraph(settings, trees, myopts, myparams,
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 10043,
> in _backtrack_depgraph
> success, favorites = mydepgraph.select_files(myfiles)
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 4055,
> in select_files
> return self._select_files(args)
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line 4189,
> in _select_files
> set_atoms = root_config.setconfig.getSetAtoms(s)
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py", line
> 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py", line
> 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py", line
> 260, in getSetAtoms
> myatoms = myset.getAtoms()
> File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line 58,
> in getAtoms
> self._load()
> File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line 53,
> in _load
> self.load()
> File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line 111,
> in load
> self._setAtoms(self.mapPathsToAtoms(self._files,
> File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line 83,
> in mapPathsToAtoms
> for p in exclude_paths:
> TypeError: 'NoneType' object is not iterable
>
> And i can't do anything else...
>
> I see that python-3.8 has gone away
> # eselect python list
> Available Python interpreters, in order of preference:
> [1] python3.9
>
> emerge --info file attached
>
> I don't really know what to do.
> Any idea ?
>
> Thanks a lot in advance,

...

I got a similar error -- I have a strange idea about this -- see if
you have any instances ofthread.isAlive( in portage or anywhere else
in your python3.9 -- if you do you need to change them to
thread.is_alive( ... python changed the name and I don't think some
people got the message -- apparently it has been depricated for quite
a while now.

Just a wild guess.

--
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
Re: Python-3.9 and emerge problems [ In reply to ]
On Fri, 18 Jun 2021 11:46:27 +0200, Jacques Montier wrote:

> #emerge --sync
> #emerge --oneshot sys-apps/portage
> #emerge -auvDN --with-bdeps=y --keep-going world
>
> I get these errors :
>
> Traceback (most recent call last):
> File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
> retval = emerge_main()
> File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1319, in
> emerge_main
> return run_action(emerge_config)
> File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line
> 3392, in run_action
> retval = action_build(emerge_config, spinner=spinner)
> File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 354,
> in action_build
> success, mydepgraph, favorites = backtrack_depgraph(
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 10005, in backtrack_depgraph
> return _backtrack_depgraph(settings, trees, myopts, myparams,
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 10043, in _backtrack_depgraph
> success, favorites = mydepgraph.select_files(myfiles)
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 4055, in select_files
> return self._select_files(args)
> File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> 4189, in _select_files
> set_atoms = root_config.setconfig.getSetAtoms(s)
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> line 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> line 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> line 260, in getSetAtoms
> myatoms = myset.getAtoms()
> File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line
> 58, in getAtoms
> self._load()
> File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line
> 53, in _load
> self.load()
> File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line
> 111, in load
> self._setAtoms(self.mapPathsToAtoms(self._files,
> File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line
> 83, in mapPathsToAtoms
> for p in exclude_paths:
> TypeError: 'NoneType' object is not iterable
>
> And i can't do anything else...
>
> I see that python-3.8 has gone away
> # eselect python list
> Available Python interpreters, in order of preference:
> [1] python3.9

I has the same a couple of days ago and had to downgrade portage from
3.0.20 to 3.0.18, by untarring the binary package to /. However, that
needed python 3.8, so I also had to untar the binary package for that.
Then I re-emerged portage-3.0.18 and python-3.8 and masked
portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with
python 3.9.

I see that portage 3.0.20-r3 is here now, so I'll try emerging that on
one system and see what happens.


--
Neil Bothwick

C Error #011: First C Program, huh?
Re: Python-3.9 and emerge problems [ In reply to ]
On Fri, 18 Jun 2021 13:07:10 +0100, Neil Bothwick wrote:

> I had the same a couple of days ago and had to downgrade portage from
> 3.0.20 to 3.0.18, by untarring the binary package to /. However, that
> needed python 3.8, so I also had to untar the binary package for that.
> Then I re-emerged portage-3.0.18 and python-3.8 and masked
> portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with
> python 3.9.
>
> I see that portage 3.0.20-r3 is here now, so I'll try emerging that on
> one system and see what happens.


Same problem with 3.0.20-r3 but then I found
https://bugs.gentoo.org/796584, changing sets.conf got rid of the issue.


--
Neil Bothwick

Of all the people I've met you're certainly one of them.
Re: Python-3.9 and emerge problems [ In reply to ]
On Fri, 18 Jun 2021 08:07:10 -0400,
Neil Bothwick wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> On Fri, 18 Jun 2021 11:46:27 +0200, Jacques Montier wrote:
>
> > #emerge --sync
> > #emerge --oneshot sys-apps/portage
> > #emerge -auvDN --with-bdeps=y --keep-going world
> >
> > I get these errors :
> >
> > Traceback (most recent call last):
> > File "/usr/lib/python-exec/python3.9/emerge", line 51, in <module>
> > retval = emerge_main()
> > File "/usr/lib/python3.9/site-packages/_emerge/main.py", line 1319, in
> > emerge_main
> > return run_action(emerge_config)
> > File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line
> > 3392, in run_action
> > retval = action_build(emerge_config, spinner=spinner)
> > File "/usr/lib/python3.9/site-packages/_emerge/actions.py", line 354,
> > in action_build
> > success, mydepgraph, favorites = backtrack_depgraph(
> > File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> > 10005, in backtrack_depgraph
> > return _backtrack_depgraph(settings, trees, myopts, myparams,
> > File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> > 10043, in _backtrack_depgraph
> > success, favorites = mydepgraph.select_files(myfiles)
> > File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> > 4055, in select_files
> > return self._select_files(args)
> > File "/usr/lib/python3.9/site-packages/_emerge/depgraph.py", line
> > 4189, in _select_files
> > set_atoms = root_config.setconfig.getSetAtoms(s)
> > File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> > line 271, in getSetAtoms
> > myatoms.update(self.getSetAtoms(s,
> > File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> > line 271, in getSetAtoms
> > myatoms.update(self.getSetAtoms(s,
> > File "/usr/lib/python3.9/site-packages/portage/_sets/__init__.py",
> > line 260, in getSetAtoms
> > myatoms = myset.getAtoms()
> > File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line
> > 58, in getAtoms
> > self._load()
> > File "/usr/lib/python3.9/site-packages/portage/_sets/base.py", line
> > 53, in _load
> > self.load()
> > File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line
> > 111, in load
> > self._setAtoms(self.mapPathsToAtoms(self._files,
> > File "/usr/lib/python3.9/site-packages/portage/_sets/dbapi.py", line
> > 83, in mapPathsToAtoms
> > for p in exclude_paths:
> > TypeError: 'NoneType' object is not iterable
> >
> > And i can't do anything else...
> >
> > I see that python-3.8 has gone away
> > # eselect python list
> > Available Python interpreters, in order of preference:
> > [1] python3.9
>
> I has the same a couple of days ago and had to downgrade portage from
> 3.0.20 to 3.0.18, by untarring the binary package to /. However, that
> needed python 3.8, so I also had to untar the binary package for that.
> Then I re-emerged portage-3.0.18 and python-3.8 and masked
> portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with
> python 3.9.
>
> I see that portage 3.0.20-r3 is here now, so I'll try emerging that on
> one system and see what happens.

No joy on doing that here -- last time I had to restore the whole
3.8 site-packages directory from before I did the emerge -- just
restoring 3.0.18 still gives me the traceback -- this is major
annoyance.

--
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
Re: Python-3.9 and emerge problems [ In reply to ]
On Fri, 18 Jun 2021 09:11:29 -0400,
Neil Bothwick wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> On Fri, 18 Jun 2021 13:07:10 +0100, Neil Bothwick wrote:
>
> > I had the same a couple of days ago and had to downgrade portage from
> > 3.0.20 to 3.0.18, by untarring the binary package to /. However, that
> > needed python 3.8, so I also had to untar the binary package for that.
> > Then I re-emerged portage-3.0.18 and python-3.8 and masked
> > portage-3.0.20. Once I had re-emerged portage-3.0.18, it worked with
> > python 3.9.
> >
> > I see that portage 3.0.20-r3 is here now, so I'll try emerging that on
> > one system and see what happens.
>
>
> 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.

--
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
Re: Python-3.9 and emerge problems [ In reply to ]
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
Re: Python-3.9 and emerge problems [ In reply to ]
* <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
Re: Python-3.9 and emerge problems [ In reply to ]
On Fri, 18 Jun 2021 10:00:17 -0400,
Neil Bothwick wrote:
>
> [1 <text/plain; US-ASCII (quoted-printable)>]
> 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.

Thanks much -- that seems to have fixed it.

--
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
Re: Python-3.9 and emerge problems [ In reply to ]
Le ven. 18 juin 2021 à 17:55, John Covici <covici@ccs.covici.com> a écrit :

> On Fri, 18 Jun 2021 10:00:17 -0400,
> Neil Bothwick wrote:
> >
> > [1 <text/plain; US-ASCII (quoted-printable)>]
> > 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.
>
> Thanks much -- that seems to have fixed it.
>
> --
> 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
>
>

Hello all,

New portage, this morning.
I commented the line exclude-files = '' in /etc/portage/sets.conf as it was
before.
Then emerge world.
Everything works fine.

Cheers,

--
Jacques