You are not logged in.

#1 2019-11-20 21:06:58

synftw
Member
Registered: 2017-02-03
Posts: 22

Updated Arch, update didn't finish because of a naming issue in a file

Everything downloaded for the update, then when updating, I got this error message. Any time I open up a terminal this message populates and I can't Ctrl+c to kill the process and return to the command line:

Traceback (most recent call last):
  File "/usr/bin/powerline-shell", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3251, in <module>
    def _initialize_master_working_set():
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3234, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'powerline-shell==0.7.0' distribution was not found and is required by the application

Here's the contents of my /usr/bin/powerline-shell, which I think is what needs to be edited, but I'm not sure and I'd rather not screw something up further.

#!/usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'powerline-shell==0.7.0','console_scripts','powerline-shell'
__requires__ = 'powerline-shell==0.7.0'
import re
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(
        load_entry_point('powerline-shell==0.7.0', 'console_scripts', 'powerline-shell')()
    )

Also because this prompt comes up every time I open a terminal I can't access vim as a superuser to edit this file. I can open Sublime through Rofi but not as a superuser.

[Solved]
git clone https://github.com/b-ryan/powerline-shell
cd powerline-shell
python setup.py install

Last edited by synftw (2019-11-21 03:24:21)

Offline

#2 2019-11-20 21:12:22

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Updated Arch, update didn't finish because of a naming issue in a file

It's your job to manage AUR packages, not pacman's. It needs to be rebuilt against the new python librs.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2019-11-20 21:14:06

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,438
Website

Re: Updated Arch, update didn't finish because of a naming issue in a file

If that's just garbage in your prompt, you can still type in commands after that backtrace.  But more importantly, you can just change to a tty and log in as root.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#4 2019-11-20 22:34:42

synftw
Member
Registered: 2017-02-03
Posts: 22

Re: Updated Arch, update didn't finish because of a naming issue in a file

jasonwryan wrote:

It's your job to manage AUR packages, not pacman's. It needs to be rebuilt against the new python librs.

I'm not sure exactly what this means. Should I wait for the developer to update their package then rebuild or should I manually change something in that file? I don't really understand the process of rebuilding a package against an updated library.

Offline

#5 2019-11-20 22:37:13

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,438
Website

Re: Updated Arch, update didn't finish because of a naming issue in a file

synftw wrote:

Should I wait for the developer to update their package then rebuild or should I manually change something in that file?

No, and no.

Just literally rebuild it.  Retrieve the AUR sources (e.g., the PKGBUILD) then from within the directory with that PKGBUILD, `makepkg -si`.  That's it.  It's exactly the same as when you first installed the AUR package.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#6 2019-11-21 00:56:10

synftw
Member
Registered: 2017-02-03
Posts: 22

Re: Updated Arch, update didn't finish because of a naming issue in a file

Trilby wrote:

Just literally rebuild it.  Retrieve the AUR sources (e.g., the PKGBUILD) then from within the directory with that PKGBUILD, `makepkg -si`.  That's it.  It's exactly the same as when you first installed the AUR package.


alright, so here's what I've done:

cd powerline-shell
git clone https://github.com/b-ryan/powerline-shell.git
makepkg -si

The result is:

==> ERROR: PKGBUILD does not exist.

Last edited by synftw (2019-11-21 00:56:43)

Offline

#7 2019-11-21 01:03:19

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,193
Website

Re: Updated Arch, update didn't finish because of a naming issue in a file


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#8 2019-11-21 01:05:25

loqs
Member
Registered: 2014-03-06
Posts: 18,730

Re: Updated Arch, update didn't finish because of a naming issue in a file

If you installed powerline-shell using sudo pip then you should remove it using pip then install it from AUR https://aur.archlinux.org/packages/powerline-shell/

Offline

#9 2019-11-21 03:15:21

synftw
Member
Registered: 2017-02-03
Posts: 22

Re: Updated Arch, update didn't finish because of a naming issue in a file

python setup.py install fixed the issue entirely.

I saw that file but didn't know how to execute. Thanks for the help.

Offline

#10 2019-11-21 14:41:03

loqs
Member
Registered: 2014-03-06
Posts: 18,730

Re: Updated Arch, update didn't finish because of a naming issue in a file

As you are installing files globally without using pacman please see Pacman#%22Failed_to_commit_transaction_(conflicting_files)%22_error

Offline

Board footer

Powered by FluxBB