Mailing List Archive: after latest update emerge completely broken

after latest update emerge completely broken

Jun 4, 2021, 4:39 AM

Post #1 of 4 (244 views)

Hi. After my latest update, when I try to emerge anything, I get the
following:
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.8/emerge", line 51, in <module>
retval = emerge_main()
File "/usr/lib/python3.8/site-packages/_emerge/main.py", line
1319, in emerge_main
return run_action(emerge_config)
File
"/usr/lib/python3.8/site-packages/_emerge/actions.py",
line 3392, in run_action
retval = action_build(emerge_config,
spinner=spinner)
File
"/usr/lib/python3.8/site-packages/_emerge/actions.py",
line 414, in action_build
retval = mydepgraph.display(
File
"/usr/lib/python3.8/site-packages/_emerge/depgraph.py",
line 8685, in display
return display(self, mylist, favorites,
verbosity)
File
"/usr/lib/python3.8/site-packages/_emerge/resolver/output.py",
line 775, in __call__
self.conf =
_DisplayConfig(depgraph, mylist,
favorites, verbosity)
File
"/usr/lib/python3.8/site-packages/_emerge/resolver/output_helpers.py",
line 201, in __init__
initial_atoms=root.setconfig.getSetAtoms("selected"))
File
"/usr/lib/python3.8/site-packages/portage/_sets/__init__.py",
line 271, in getSetAtoms
myatoms.update(self.getSetAtoms(s,
File
"/usr/lib/python3.8/site-packages/portage/_sets/__init__.py",
line 260, in
getSetAtoms
myatoms =
myset.getAtoms()
File
"/usr/lib/python3.8/site-packages/portage/_sets/base.py",
line 58, in
getAtoms
self._load()
File
"/usr/lib/python3.8/site-packages/portage/_sets/base.py",
line 53,
in _load
self.load()
File
"/usr/lib/python3.8/site-packages/portage/_sets/dbapi.py",
line
111,
in
load
self._setAtoms(self.mapPathsToAtoms(self._files,
File
"/usr/lib/python3.8/site-packages/portage/_sets/dbapi.py",
line
83,
in
mapPathsToAtoms
for
p
in
exclude_paths:
TypeError:
'NoneType'
object
is
not
iterable

I have binary packages for lots of things, including portage if I need
it, but no way to emerge any of them.

Thanks in advance for any suggestions.

--
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: after latest update emerge completely broken [ In reply to ]

covici at ccs

Jun 4, 2021, 6:53 PM

Post #2 of 4 (244 views)

Permalink

On Fri, 04 Jun 2021 07:39:25 -0400,
John Covici wrote:
>
> Hi. After my latest update, when I try to emerge anything, I get the
> following:
> Traceback (most recent call last):
> File "/usr/lib/python-exec/python3.8/emerge", line 51, in <module>
> retval = emerge_main()
> File "/usr/lib/python3.8/site-packages/_emerge/main.py", line
> 1319, in emerge_main
> return run_action(emerge_config)
> File
> "/usr/lib/python3.8/site-packages/_emerge/actions.py",
> line 3392, in run_action
> retval = action_build(emerge_config,
> spinner=spinner)
> File
> "/usr/lib/python3.8/site-packages/_emerge/actions.py",
> line 414, in action_build
> retval = mydepgraph.display(
> File
> "/usr/lib/python3.8/site-packages/_emerge/depgraph.py",
> line 8685, in display
> return display(self, mylist, favorites,
> verbosity)
> File
> "/usr/lib/python3.8/site-packages/_emerge/resolver/output.py",
> line 775, in __call__
> self.conf =
> _DisplayConfig(depgraph, mylist,
> favorites, verbosity)
> File
> "/usr/lib/python3.8/site-packages/_emerge/resolver/output_helpers.py",
> line 201, in __init__
> initial_atoms=root.setconfig.getSetAtoms("selected"))
> File
> "/usr/lib/python3.8/site-packages/portage/_sets/__init__.py",
> line 271, in getSetAtoms
> myatoms.update(self.getSetAtoms(s,
> File
> "/usr/lib/python3.8/site-packages/portage/_sets/__init__.py",
> line 260, in
> getSetAtoms
> myatoms =
> myset.getAtoms()
> File
> "/usr/lib/python3.8/site-packages/portage/_sets/base.py",
> line 58, in
> getAtoms
> self._load()
> File
> "/usr/lib/python3.8/site-packages/portage/_sets/base.py",
> line 53,
> in _load
> self.load()
> File
> "/usr/lib/python3.8/site-packages/portage/_sets/dbapi.py",
> line
> 111,
> in
> load
> self._setAtoms(self.mapPathsToAtoms(self._files,
> File
> "/usr/lib/python3.8/site-packages/portage/_sets/dbapi.py",
> line
> 83,
> in
> mapPathsToAtoms
> for
> p
> in
> exclude_paths:
> TypeError:
> 'NoneType'
> object
> is
> not
> iterable
>
> I have binary packages for lots of things, including portage if I need
> it, but no way to emerge any of them.
>
>
> Thanks in advance for any suggestions.

I have an update. I was able to get emerge to work again by unpacking
a binary package of portage into /usr/lib/python3.8 but if I try to
emerge portage again, I get that traceback again. Is portage 0.3.19
broke?

--
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: after latest update emerge completely broken [ In reply to ]

billk at iinet

Jun 4, 2021, 11:09 PM

Post #3 of 4 (244 views)

Permalink

On 5/6/21 9:53 am, John Covici wrote:
> On Fri, 04 Jun 2021 07:39:25 -0400,
> John Covici wrote:
>> I have binary packages for lots of things, including portage if I need
>> it, but no way to emerge any of them.
>>
>>
>> Thanks in advance for any suggestions.
> I have an update. I was able to get emerge to work again by unpacking
> a binary package of portage into /usr/lib/python3.8 but if I try to
> emerge portage again, I get that traceback again. Is portage 0.3.19
> broke?
>
Are the binary package files from an emerge buildpkg or quickpkg? - if
so you can untar them in / to restore the files (do you have a buildpkg
of 3.0.18 - stable version?). Its not a true install but this method
has saved me a number of times from snafu's like this.

BillK

Re: after latest update emerge completely broken [ In reply to ]

covici at ccs

Jun 4, 2021, 11:48 PM

Post #4 of 4 (244 views)

Permalink

On Sat, 05 Jun 2021 02:09:32 -0400,
William Kenworthy wrote:
>
>
> On 5/6/21 9:53 am, John Covici wrote:
> > On Fri, 04 Jun 2021 07:39:25 -0400,
> > John Covici wrote:
> >> I have binary packages for lots of things, including portage if I need
> >> it, but no way to emerge any of them.
> >>
> >>
> >> Thanks in advance for any suggestions.
> > I have an update. I was able to get emerge to work again by unpacking
> > a binary package of portage into /usr/lib/python3.8 but if I try to
> > emerge portage again, I get that traceback again. Is portage 0.3.19
> > broke?
> >
> Are the binary package files from an emerge buildpkg or quickpkg? - if
> so you can untar them in / to restore the files (do you have a buildpkg
> of 3.0.18 - stable version?).? Its not a true install but this method
> has saved me a number of times from snafu's like this.

Exactly, it was a .bz2 file which I just copied everything from its
usr directory into /usr and that saved a certain portion of my
anatomy.

Also, the python was set to 3.9 even though I forced 3.8 in my package
.use -- I did set it back, but that by itself did not fix the problem.

--
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