You are not logged in.
- Topics: Active | Unanswered
#1 2024-11-16 02:59:56
- Straight-path
- Member
- Registered: 2020-06-28
- Posts: 62
I think some fool has put pip in an aur package
Hi
Yeah, most likely will make mistakes in this post as from negative previous experience and knowledge I don't post here but.... lol I'm well angry.
Want to report this or get it sorted. Obviously don't know the channels.
I'll be either reinstalling from rsync or new installation. Spent the night messing with this crap.
from chat convo:
what package caused all this shit with pip?
ChatGPT said:
The cause of the pip chaos on your system appears to stem from an AUR package that executed pip commands globally during its build or installation process. This is against Arch's packaging standards, as AUR packages are supposed to manage all Python dependencies via pacman and not directly invoke pip.
Likely Culprits
From your earlier package list and pip issues, the following AUR packages are the most likely offenders:
python-pyvips:
This is a Python binding for the libvips library. AUR packages like this sometimes build wheels (.whl) and install dependencies globally using pip.
It directly involves Python packages like pycairo.
miniaturo-git:
A lightweight image viewer that could have used pip to install dependencies like pyvips or PyQt5.
qtile:
A Python-based tiling window manager that requires Qt bindings like PySide6 or PyQt5. If it was built via AUR, the PKGBUILD may have invoked pip.
Identifying the Offender
1. Check the PKGBUILD of Installed AUR Packages
You can review the PKGBUILD of each AUR package you installed to see if it contains problematic pip commands:
For example, retrieve and inspect the PKGBUILD for python-pyvips:
bash
Copy code
yay -G python-pyvips
cd python-pyvips
cat PKGBUILD
Look for pip install commands in the prepare(), build(), or package() functions.
2. Look for Unmanaged Pip Packages
Check if a specific AUR package owns the problematic pip packages:
bash
Copy code
pacman -Qo /usr/lib/python3.12/site-packages/pycairo
If no package claims ownership, the package was likely installed directly by pip.
3. Check Installation Logs
Search for logs of the offending package installation:
If you used yay:
bash
Copy code
cat ~/.cache/yay/<package-name>/log
Replace <package-name> with suspected offenders like python-pyvips or miniaturo-git. Look for pip install commands in the log.
Common Patterns in AUR Pip Issues
A poorly written PKGBUILD might have:
Globally installed dependencies with pip instead of pacman.
Neglected to use pip install --target=<custom_dir> to isolate Python dependencies.
Next Steps
Fix the AUR Package:
If you find that a PKGBUILD is responsible, you can fix it by editing the PKGBUILD to avoid global pip installs. Report the issue to the package maintainer on the AUR webpage.
Rebuild the Package Correctly:
After fixing the PKGBUILD, rebuild the package:
bash
Copy code
makepkg -si
Avoid Packages with Poor Practices:
Before installing an AUR package, inspect its PKGBUILD for poor practices, especially global pip usage.
Reporting the Issue
If you determine which package caused the problem, report the issue on its AUR package page. Include details about:
How it installed Python dependencies with pip.
The mess it caused on your system.
This helps maintain a higher quality standard for AUR packages.mess from my terminal
sudo pacman -Rns python-pyvips [2:26:48]
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing python-pyvips breaks dependency 'python-pyvips' required by folderpreview
slim:~/ $ sudo pacman -Rns python-pyvips folderpreview [2:26:58]
checking dependencies...
:: python-wheel optionally requires python-xdg: for wheel.signatures
:: qtile optionally requires python-dbus-next: for utils, notifications and several widgets
:: qtile optionally requires python-xdg: launchbar widget
Packages (11) cfitsio-1:4.5.0-1 libcgif-0.4.1-1 libvips-8.16.0-2 python-colorlog-6.8.2-2 python-dbus-next-0.2.3-5 python-parse-1.20.2-1 python-pkgconfig-1.5.5-6
python-pyxdg-0.28-3 python-systemd-235-3 folderpreview-0.4.3-1 python-pyvips-2.2.3-1
Total Removed Size: 14.11 MiB
:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
( 1/11) removing folderpreview [##############################################################] 100%
( 2/11) removing python-systemd [##############################################################] 100%
( 3/11) removing python-pyxdg [##############################################################] 100%
( 4/11) removing python-parse [##############################################################] 100%
( 5/11) removing python-dbus-next [##############################################################] 100%
( 6/11) removing python-colorlog [##############################################################] 100%
( 7/11) removing python-pyvips [##############################################################] 100%
( 8/11) removing python-pkgconfig [##############################################################] 100%
( 9/11) removing libvips [##############################################################] 100%
(10/11) removing libcgif [##############################################################] 100%
(11/11) removing cfitsio [##############################################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
slim:~/ $ pip list [2:27:54]
Package Version
---------------------------- -------------------------------
annotated-types 0.7.0
appdirs 1.4.4
asciidoc 10.2.1
attrs 23.2.1.dev0
autocommand 2.2.2
beautifulsoup4 4.12.3
build 1.2.2
CacheControl 0.14.1
cairocffi 1.6.1
catfish 4.18.0
certifi 2024.8.30
cffi 1.17.1
chardet 5.2.0
charset-normalizer 3.4.0
coverage 7.6.3
cryptography 42.0.8
cssselect 1.2.0
dbus-python 1.3.2
defusedxml 0.7.1
docopt 0.6.2
filelock 3.13.3
Glances 4.2.1
gufw 24.4.0
idna 3.10
installer 0.7.0
jaraco.collections 5.0.1
jaraco.context 5.3.0
jaraco.functools 4.0.2
jaraco.text 4.0.0
Jinja2 3.1.4
keyutils 0.6
lightdm-gtk-greeter-settings 1.2.3
lit 18.1.8.dev0
lockfile 0.12.2
lxml 5.3.0
MarkupSafe 2.1.5
mcomix 3.1.0
more-itertools 10.3.0
msgpack 1.0.5
numpy 2.1.3
orjson 3.10.11
packaging 24.1
pexpect 4.9.0
pillow 11.0.0
pip 24.3.1
platformdirs 4.3.6
psutil 6.1.0
ptyprocess 0.7.0
pulsemixer 1.5.1
pybind11 2.13.6
pycairo 1.27.0
pycparser 2.22
pydantic 2.9.2
pydantic_core 2.23.4
PyGObject 3.50.0
PyOpenGL 3.1.7
pyproject_hooks 1.2.0
PyQt5 5.15.11
PyQt5_sip 12.15.0
pyserial 3.5
PySide6 6.8.0.2
PyYAML 6.0.2
qtile 0.29.1.dev0+geed1e03c.d20241021
Reflector 2023.6.28.0.36.1
requests 2.32.3
scour 0.38.2
setuptools 75.2.0
shiboken6 6.8.0.2
shiboken6-generator 6.8.0.2
six 1.16.0
soupsieve 2.6
TBB 0.2
typing_extensions 4.12.2
udiskie 2.5.3
ufw 0.36.2
urllib3 1.26.20
wheel 0.44.0
xcffib 1.5.0
zstandard 0.22.0
slim:~/ $ sudo pacman -Rns miniaturo-git [2:27:58]
checking dependencies...
:: gdk-pixbuf2 optionally requires libopenraw: Load .dng, .cr2, .crw, .nef, .orf, .pef, .arw, .erf, .mrw, and .raf
:: tumbler optionally requires libopenraw: RAW thumbnails
Packages (2) libopenraw-0.3.7-2 miniaturo-git-0.6.0.r0.g84dce0c-1
Total Removed Size: 4.52 MiB
:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
(1/2) removing miniaturo-git [##############################################################] 100%
(2/2) removing libopenraw [##############################################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Probing GDK-Pixbuf loader modules...
slim:~/ $ pip list [2:28:32]
Package Version
---------------------------- -------------------------------
annotated-types 0.7.0
appdirs 1.4.4
asciidoc 10.2.1
attrs 23.2.1.dev0
autocommand 2.2.2
beautifulsoup4 4.12.3
build 1.2.2
CacheControl 0.14.1
cairocffi 1.6.1
catfish 4.18.0
certifi 2024.8.30
cffi 1.17.1
chardet 5.2.0
charset-normalizer 3.4.0
coverage 7.6.3
cryptography 42.0.8
cssselect 1.2.0
dbus-python 1.3.2
defusedxml 0.7.1
docopt 0.6.2
filelock 3.13.3
Glances 4.2.1
gufw 24.4.0
idna 3.10
installer 0.7.0
jaraco.collections 5.0.1
jaraco.context 5.3.0
jaraco.functools 4.0.2
jaraco.text 4.0.0
Jinja2 3.1.4
keyutils 0.6
lightdm-gtk-greeter-settings 1.2.3
lit 18.1.8.dev0
lockfile 0.12.2
lxml 5.3.0
MarkupSafe 2.1.5
mcomix 3.1.0
more-itertools 10.3.0
msgpack 1.0.5
numpy 2.1.3
orjson 3.10.11
packaging 24.1
pexpect 4.9.0
pillow 11.0.0
pip 24.3.1
platformdirs 4.3.6
psutil 6.1.0
ptyprocess 0.7.0
pulsemixer 1.5.1
pybind11 2.13.6
pycairo 1.27.0
pycparser 2.22
pydantic 2.9.2
pydantic_core 2.23.4
PyGObject 3.50.0
PyOpenGL 3.1.7
pyproject_hooks 1.2.0
PyQt5 5.15.11
PyQt5_sip 12.15.0
pyserial 3.5
PySide6 6.8.0.2
PyYAML 6.0.2
qtile 0.29.1.dev0+geed1e03c.d20241021
Reflector 2023.6.28.0.36.1
requests 2.32.3
scour 0.38.2
setuptools 75.2.0
shiboken6 6.8.0.2
shiboken6-generator 6.8.0.2
six 1.16.0
soupsieve 2.6
TBB 0.2
typing_extensions 4.12.2
udiskie 2.5.3
ufw 0.36.2
urllib3 1.26.20
wheel 0.44.0
xcffib 1.5.0
zstandard 0.22.0
slim:~/ $ pip freeze | xargs pip uninstall -y [2:28:36]
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try 'pacman -S
python-xyz', where xyz is the package you are trying to
install.
If you wish to install a non-Arch-packaged Python package,
create a virtual environment using 'python -m venv path/to/venv'.
Then use path/to/venv/bin/python and path/to/venv/bin/pip.
If you wish to install a non-Arch packaged Python application,
it may be easiest to use 'pipx install xyz', which will manage a
virtual environment for you. Make sure you have python-pipx
installed via pacman.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
slim:~/ $ pip freeze | xargs pip uninstall -y --break-system-packages [2:30:25]
Found existing installation: annotated-types 0.7.0
Uninstalling annotated-types-0.7.0:
ERROR: Exception:
Traceback (most recent call last):
File "/usr/lib/python3.12/shutil.py", line 847, in move
os.rename(src, real_dst)
OSError: [Errno 18] Invalid cross-device link: '/usr/lib/python3.12/site-packages/annotated_types-0.7.0.dist-info/' -> '/tmp/pip-uninstall-h3ymowl7'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.12/site-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper
status = _inner_run()
^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run
return self.run(options, args)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/pip/_internal/commands/uninstall.py", line 106, in run
uninstall_pathset = req.uninstall(
^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/pip/_internal/req/req_install.py", line 723, in uninstall
uninstalled_pathset.remove(auto_confirm, verbose)
File "/usr/lib/python3.12/site-packages/pip/_internal/req/req_uninstall.py", line 370, in remove
moved.stash(path)
File "/usr/lib/python3.12/site-packages/pip/_internal/req/req_uninstall.py", line 261, in stash
renames(path, new_path)
File "/usr/lib/python3.12/site-packages/pip/_internal/utils/misc.py", line 349, in renames
shutil.move(old, new)
File "/usr/lib/python3.12/shutil.py", line 865, in move
rmtree(src)
File "/usr/lib/python3.12/shutil.py", line 759, in rmtree
_rmtree_safe_fd(stack, onexc)
File "/usr/lib/python3.12/shutil.py", line 703, in _rmtree_safe_fd
onexc(func, path, err)
File "/usr/lib/python3.12/shutil.py", line 700, in _rmtree_safe_fd
onexc(os.unlink, fullname, err)
File "/usr/lib/python3.12/shutil.py", line 698, in _rmtree_safe_fd
os.unlink(entry.name, dir_fd=topfd)
PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.12/site-packages/annotated_types-0.7.0.dist-info/'
slim:~/ $ sudo pip freeze | xargs sudo pip uninstall -y --break-system-packages [2:31:25]
Found existing installation: annotated-types 0.7.0
Uninstalling annotated-types-0.7.0:
Successfully uninstalled annotated-types-0.7.0
Found existing installation: appdirs 1.4.4
Uninstalling appdirs-1.4.4:
Successfully uninstalled appdirs-1.4.4
Found existing installation: asciidoc 10.2.1
Uninstalling asciidoc-10.2.1:
Successfully uninstalled asciidoc-10.2.1
Found existing installation: attrs 23.2.1.dev0
Uninstalling attrs-23.2.1.dev0:
Successfully uninstalled attrs-23.2.1.dev0
Found existing installation: autocommand 2.2.2
Uninstalling autocommand-2.2.2:
Successfully uninstalled autocommand-2.2.2
Found existing installation: beautifulsoup4 4.12.3
Uninstalling beautifulsoup4-4.12.3:
Successfully uninstalled beautifulsoup4-4.12.3
Found existing installation: build 1.2.2
Uninstalling build-1.2.2:
Successfully uninstalled build-1.2.2
Found existing installation: CacheControl 0.14.1
Uninstalling CacheControl-0.14.1:
Successfully uninstalled CacheControl-0.14.1
Found existing installation: cairocffi 1.6.1
Uninstalling cairocffi-1.6.1:
Successfully uninstalled cairocffi-1.6.1
Found existing installation: catfish 4.18.0
Uninstalling catfish-4.18.0:
Successfully uninstalled catfish-4.18.0
Found existing installation: certifi 2024.8.30
Uninstalling certifi-2024.8.30:
Successfully uninstalled certifi-2024.8.30
Found existing installation: cffi 1.17.1
Uninstalling cffi-1.17.1:
Successfully uninstalled cffi-1.17.1
Found existing installation: chardet 5.2.0
Uninstalling chardet-5.2.0:
Successfully uninstalled chardet-5.2.0
Found existing installation: charset-normalizer 3.4.0
Uninstalling charset-normalizer-3.4.0:
Successfully uninstalled charset-normalizer-3.4.0
Found existing installation: coverage 7.6.3
Uninstalling coverage-7.6.3:
Successfully uninstalled coverage-7.6.3
Found existing installation: cryptography 42.0.8
Uninstalling cryptography-42.0.8:
Successfully uninstalled cryptography-42.0.8
Found existing installation: cssselect 1.2.0
Uninstalling cssselect-1.2.0:
Successfully uninstalled cssselect-1.2.0
Found existing installation: dbus-python 1.3.2
Can't uninstall 'dbus-python'. No files were found to uninstall.
Found existing installation: defusedxml 0.7.1
Uninstalling defusedxml-0.7.1:
Successfully uninstalled defusedxml-0.7.1
Found existing installation: docopt 0.6.2
Uninstalling docopt-0.6.2:
Successfully uninstalled docopt-0.6.2
Found existing installation: filelock 3.13.3
Uninstalling filelock-3.13.3:
Successfully uninstalled filelock-3.13.3
Found existing installation: Glances 4.2.1
Uninstalling Glances-4.2.1:
Successfully uninstalled Glances-4.2.1
Found existing installation: gufw 24.4.0
Uninstalling gufw-24.4.0:
Successfully uninstalled gufw-24.4.0
Found existing installation: idna 3.10
Uninstalling idna-3.10:
Successfully uninstalled idna-3.10
Found existing installation: installer 0.7.0
Uninstalling installer-0.7.0:
Successfully uninstalled installer-0.7.0
Found existing installation: jaraco.collections 5.0.1
Uninstalling jaraco.collections-5.0.1:
Successfully uninstalled jaraco.collections-5.0.1
Found existing installation: jaraco.context 5.3.0
Uninstalling jaraco.context-5.3.0:
Successfully uninstalled jaraco.context-5.3.0
Found existing installation: jaraco.functools 4.0.2
Uninstalling jaraco.functools-4.0.2:
Successfully uninstalled jaraco.functools-4.0.2
Found existing installation: jaraco.text 4.0.0
Uninstalling jaraco.text-4.0.0:
Successfully uninstalled jaraco.text-4.0.0
Found existing installation: Jinja2 3.1.4
Uninstalling Jinja2-3.1.4:
Successfully uninstalled Jinja2-3.1.4
Found existing installation: keyutils 0.6
Uninstalling keyutils-0.6:
Successfully uninstalled keyutils-0.6
Found existing installation: lightdm-gtk-greeter-settings 1.2.3
Uninstalling lightdm-gtk-greeter-settings-1.2.3:
Successfully uninstalled lightdm-gtk-greeter-settings-1.2.3
Found existing installation: lit 18.1.8.dev0
Uninstalling lit-18.1.8.dev0:
Successfully uninstalled lit-18.1.8.dev0
Found existing installation: lockfile 0.12.2
Uninstalling lockfile-0.12.2:
Successfully uninstalled lockfile-0.12.2
Found existing installation: lxml 5.3.0
Uninstalling lxml-5.3.0:
Successfully uninstalled lxml-5.3.0
Found existing installation: MarkupSafe 2.1.5
Uninstalling MarkupSafe-2.1.5:
Successfully uninstalled MarkupSafe-2.1.5
Found existing installation: mcomix 3.1.0
Uninstalling mcomix-3.1.0:
Successfully uninstalled mcomix-3.1.0
Found existing installation: more-itertools 10.3.0
Uninstalling more-itertools-10.3.0:
Successfully uninstalled more-itertools-10.3.0
Found existing installation: msgpack 1.0.5
Uninstalling msgpack-1.0.5:
Successfully uninstalled msgpack-1.0.5
Found existing installation: numpy 2.1.3
Uninstalling numpy-2.1.3:
Successfully uninstalled numpy-2.1.3
Found existing installation: orjson 3.10.11
Uninstalling orjson-3.10.11:
Successfully uninstalled orjson-3.10.11
Found existing installation: packaging 24.1
Uninstalling packaging-24.1:
Successfully uninstalled packaging-24.1
Found existing installation: pexpect 4.9.0
Uninstalling pexpect-4.9.0:
Successfully uninstalled pexpect-4.9.0
Found existing installation: pillow 11.0.0
Uninstalling pillow-11.0.0:
Successfully uninstalled pillow-11.0.0
Found existing installation: platformdirs 4.3.6
Uninstalling platformdirs-4.3.6:
Successfully uninstalled platformdirs-4.3.6
Found existing installation: psutil 6.1.0
Uninstalling psutil-6.1.0:
Successfully uninstalled psutil-6.1.0
Found existing installation: ptyprocess 0.7.0
Uninstalling ptyprocess-0.7.0:
Successfully uninstalled ptyprocess-0.7.0
Found existing installation: pulsemixer 1.5.1
Uninstalling pulsemixer-1.5.1:
Successfully uninstalled pulsemixer-1.5.1
Found existing installation: pybind11 2.13.6
Uninstalling pybind11-2.13.6:
Successfully uninstalled pybind11-2.13.6
Found existing installation: pycairo 1.27.0
error: uninstall-no-record-file
× Cannot uninstall pycairo 1.27.0
╰─> The package's contents are unknown: no RECORD file was found for pycairo.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps pycairo==1.27.0
slim:~/ $ sudo pip install --force-reinstall --no-deps pycairo==1.27.0 --break-system-packages [2:32:01]
Collecting pycairo==1.27.0
Downloading pycairo-1.27.0.tar.gz (661 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 661.5/661.5 kB 5.4 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: pycairo
Building wheel for pycairo (pyproject.toml) ... done
Created wheel for pycairo: filename=pycairo-1.27.0-cp312-cp312-linux_x86_64.whl size=130163 sha256=1b4cc4874a5fef4ddf72e565755844ba48e7a19dde5c0bfd77584045d88a290d
Stored in directory: /root/.cache/pip/wheels/46/bc/8a/4f565f6dc8b58ba11b65834c6a6e679cf798040a2af304c281
Successfully built pycairo
Installing collected packages: pycairo
Attempting uninstall: pycairo
Found existing installation: pycairo 1.27.0
error: uninstall-no-record-file
× Cannot uninstall pycairo 1.27.0
╰─> The package's contents are unknown: no RECORD file was found for pycairo.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps pycairo==1.27.0
slim:~/ $ sudo pip uninstall pycairo --break-system-packages [2:33:25]
Found existing installation: pycairo 1.27.0
error: uninstall-no-record-file
× Cannot uninstall pycairo 1.27.0
╰─> The package's contents are unknown: no RECORD file was found for pycairo.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps pycairo==1.27.0
slim:~/ $ sudo pip install --force-reinstall dbus-python --break-system-packages [2:33:36]
Collecting dbus-python
Downloading dbus-python-1.3.2.tar.gz (605 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 605.5/605.5 kB 5.1 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: dbus-python
Building wheel for dbus-python (pyproject.toml) ... done
Created wheel for dbus-python: filename=dbus_python-1.3.2-cp312-cp312-linux_x86_64.whl size=122258 sha256=246498b3f54ec44c47424e604a9c0e81b57d530383060818437a2cbfefad8e29
Stored in directory: /root/.cache/pip/wheels/af/10/cf/199cea3104083e08fd54f5f1d61656138c62b9677b0f78f1b6
Successfully built dbus-python
Installing collected packages: dbus-python
Attempting uninstall: dbus-python
Found existing installation: dbus-python 1.3.2
Can't uninstall 'dbus-python'. No files were found to uninstall.
Successfully installed dbus-python-1.3.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
slim:~/ $ sudo pip uninstall dbus-python --break-system-packages [2:34:00]
Found existing installation: dbus-python 1.3.2
Uninstalling dbus-python-1.3.2:
Would remove:
/usr/include/python3.12/dbus-python/dbus-1.0/dbus/dbus-python.h
/usr/lib/python3.12/site-packages/.dbus_python.mesonpy.libs/pkgconfig/dbus-python.pc
/usr/lib/python3.12/site-packages/_dbus_bindings.cpython-312-x86_64-linux-gnu.so
/usr/lib/python3.12/site-packages/_dbus_glib_bindings.cpython-312-x86_64-linux-gnu.so
/usr/lib/python3.12/site-packages/dbus/*
/usr/lib/python3.12/site-packages/dbus_python-1.3.2.dist-info/*
Would not remove (might be manually added):
/usr/lib/python3.12/site-packages/dbus/mainloop/pyqt5.abi3.so
Proceed (Y/n)? y
Successfully uninstalled dbus-python-1.3.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. I remember seeing pip from an installation of an aur package but not sure which one it is. Chat mentioned before it thinks the likely culprits of the pip installation are python-pyvips or miniaturo-git or qtile.
pacman -Qm [2:56:21]
miniaturo-git-debug 0.6.0.r0.g84dce0c-1
mojave-gtk-theme 2023_08_04-1
obexftp 0.24.2-6
obexftp-debug 0.24.2-6
openobex 1.7.2-5
openobex-debug 1.7.2-5
python-pyvips-debug 2.2.3-1
python2 2.7.18-11
python2-debug 2.7.18-11
ttf-symbola-free 9.00-1
ttf-twemoji-color 15.1.0-1
tumbler-extra-thumbnailers 5.1-1
yay-debug 12.4.2-1 probably not very helpful. apologies for lack of information etc. Like i said... I don't post but this one pissed me off proper!
I'll wait about an hour before doing the reinstall or rsync etc.
Last edited by Straight-path (2024-11-16 03:01:52)
Offline
#2 2024-11-16 04:04:50
- Awebb
- Member
- Registered: 2010-05-06
- Posts: 6,613
Re: I think some fool has put pip in an aur package
If you want to report this, go over every foreign package's PKGBUILD on aur.archlinux.org and see if there is a pip execution. You could also clone into all of them and grep your way through it or grep over yay's cache, if it has one.
However, chances are ChatGTP is full of shit, as the packes you two suspected are clean.
Offline
#3 2024-11-16 04:18:03
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 12,116
Re: I think some fool has put pip in an aur package
As PKGBUILDs don't run as root, they can't execute pip globally. ChatGPT is, as usual, full of shit. I do see *you* running pip as root, though, so that's likely where your mess came from. What's the actual problem you're trying to solve here?
Last edited by Scimmia (2024-11-16 04:39:35)
Online
#4 2024-11-16 04:36:58
- Awebb
- Member
- Registered: 2010-05-06
- Posts: 6,613
Re: I think some fool has put pip in an aur package
What's the actual problem you're trying to solve here?
I guess this is some sort of scratchpad style thread, because
Want to report this or get it sorted. Obviously don't know the channels.
If this really was some mess created by a package, it should be reported. But - holy crap! - I've now read the ChatGTP output and it is indeed hallucinating:
AUR packages like this sometimes build wheels (.whl) and install dependencies globally using pip.
A wild goose chase, Straight-path. Loading a backup or re-installing could be quicker than sorting the mess. I also suggest looking into something like btrfs and snapshots (if you're re-installing anyway), that way it'll be easier to roll back the system in case you run into something similar again.
Offline
#5 2024-11-16 08:24:39
- seth
- Member
- Registered: 2012-09-03
- Posts: 58,981
Re: I think some fool has put pip in an aur package
pacman -Qo pip
pacman -Qi python-pip python-pipx will tell you why it's installed.
Alternatively check you pacman log.
Also wtf are you doing there?
You removed some packages, check the installed python modules w/ pip (it will list modules installed w/ pacman) and then starts the foolish part that involves your fingers, sudo and "--break-system-packages" - so we've at least identified one fool in the process.
==> What problem were you actually trying to solve before you created this mess?
Offline
#6 2024-11-16 13:35:24
- Straight-path
- Member
- Registered: 2020-06-28
- Posts: 62
Re: I think some fool has put pip in an aur package
Wow and hello lol.
I hope you all are well!
Did for sure made me smile and laugh reading above.
I thank you all for your replies. lol minus Seth.
I have no problem saying it, I reckon most likely I'm the biggest noob who uses Arch. lol a sucker for pain I don't know but yeah, arch doesn't beat me, I never, ever, back down or give up.
I learnt long time back if I want to install stuff with pip then to do it in a venv. I definitiley did see pip installing after running yay at some point and installing an aur package, sadly didn't give much mind to it at the time until later when I had an issue with picom+transparency. I can't even remember now specifically tbh what led me to realise the issue with pip and the globally installed pip packages.
It was definitely because I was spending hours trying to troubleshoot my issue with picom. The issue I was having was that I was getting transparency with kitty but nothing else. aaaaaahhhh lol I remember now. I noticed there was another instance of picom everytime I booted up the system. I learnt from chat that it was a zombie process and that it was started by a parent process which had something to do with the pip packages. Then I remembered what I had seen when installing that aur package (but not which package it was sadly).
I know for sure I wasn't starting the other instance of picom... I didn't have an .xinitrc or .xprofile or an autostart.sh doing it. I was just starting picom from the qtile config.py.
I think picom as undergone some changes so I'll have to do some more research as I have the same issue on my new install. I think it's got something to do with the rules section, lol but that's about it.
Yes Seth, I was destroying my system in that output you can see. Lol by that point.... the whole night later.... I had had enough and was lol, I don't know, trying to brute force lol it to fix. Trying to uninstall the packages etc.
I have used snapper with btrfs and timeshift with ext4 but have found I prefer just running my rsync command. lol Like with everything I have eventually learnt, I just memorised that command.
Yeah for sure I have let Chat chat too much crap and take me down too many rabbit holes unnecessarily, but I definitely did notice the pip after running yay and I definitely did not run pip in the beginning with sudo to get those packages.
As PKGBUILDs don't run as root, they can't execute pip globally. ChatGPT is, as usual, full of shit. I do see *you* running pip as root, though, so that's likely where your mess came from. What's the actual problem you're trying to solve here?
Mmmhh, yeah if what you said is correct then lol well, I just don't know. I did not run sudo pip first. I first ran pip list and saw all the packages. lol in the past I have done and in the past doing so led me to learn about using venv's.
Anyway guys, I thank you all, (including Seth for your commands you gave, which I will note down,) for your time and answers. Has actually made me rethink and I may post here again in the future.
I've tried many Arch based distros but have always just returned to Arch. I like a system that I have put together so I know whats what, lol I get too confused when its been done some other guys way. lol also the amount of times I've installed Arch I literally can install it in about 20 mins without looking at the wiki once.
Sadly in the end I just scrapped the whole system and reinstalled even tho I could have gone back to an earlier rsync backup because doing so I would have had to do some figuring with the aur packages. From that issue I realised that the rsync command and aur packages don't work well together and in the future I'll have to make a list of my aur packages and reinstall them or something, not sure yet tbh. I had aur packages which weren't there when I ran the rsync command.
FYI this i my rsync command
rsync -aAXHv --delete --exclude='/rsyncbk/*' --exclude='/ssd/*' --exclude='/dev/*' --exclude='/proc/*' --exclude='/sys/*' --exclude='/tmp/*' --exclude='/run/*' --exclude='/mnt/*' --exclude='/media/*' --exclude='/lost+found/' --exclude='/home/slim/.thumbnails/*' --exclude='/home/slim/.cache/*' --exclude='/home/slim/.local/share/Trash/*' --exclude='/home/slim/.gvfs' --exclude='/var/lib/dhcpcd/*' --exclude='/home/slim/Desktop/*' --exclude='/home/slim/Documents/*' --exclude='/home/slim/Downloads/*' --exclude='/home/slim/Music/*' --exclude='/home/slim/Pictures/*' --exclude='/home/slim/Public/*' --exclude='/home/slim/Templates/*' --exclude='/home/slim/Videos/*' / /rsyncbk/firstbk Offline
#7 2024-11-16 15:03:49
- seth
- Member
- Registered: 2012-09-03
- Posts: 58,981
Re: I think some fool has put pip in an aur package
The issue I was having was that I was getting transparency with kitty but nothing else. aaaaaahhhh lol I remember now. I noticed there was another instance of picom everytime I booted up the system. I learnt from chat that it was a zombie process and that it was started by a parent process which had something to do with the pip packages. Then I remembered what I had seen when installing that aur package (but not which package it was sadly).
This is complete nonsense.
1. stop paying any attention to ShitGPT, it's very good at formulating eloquent english sentences and absolutely nothing else.
2. windows will be transparent because either they're ARGB visuals with an actual alpha channel or there's a hint to or setting in the conpositor to make them or parts of them transparent
3. the fact that kitty was transparent means that there was a working compositor (most likely picom)
If you run into this again, please open a new thread so we can look into the situation at had.
Do not follow any DumbGPT advice again - as you might have noticed, you're just running into more trouble this way.
Offline