@zeroconf would re-installing python-setuptools fix the issue?
EDIT: might have to remove that empty database directory first, then re-install
Git Clone URL: | https://aur.archlinux.org/yay.git (read-only, click to copy) |
---|---|
Package Base: | yay |
Description: | Yet another yogurt. Pacman wrapper and AUR helper written in go. |
Upstream URL: | https://github.com/Jguer/yay |
Keywords: | arm AUR go helper pacman wrapper x86 |
Licenses: | GPL-3.0-or-later |
Submitter: | jguer |
Maintainer: | jguer |
Last Packager: | jguer |
Votes: | 2251 |
Popularity: | 23.44 |
First Submitted: | 2016-10-05 17:20 (UTC) |
Last Updated: | 2024-09-19 14:27 (UTC) |
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 35 Next › Last »
@zeroconf would re-installing python-setuptools fix the issue?
EDIT: might have to remove that empty database directory first, then re-install
Any idea, why querying locally will issue such error? Hopefully can it be fixed. I understand, that file is missing but it is not in my power to fix it.
yay -Qs yay
error: could not open file /var/lib/pacman/local/python-setuptools-1:63.4.1-1/desc: No such file or directory
local/yay 11.3.0-1
Yet another yogurt. Pacman wrapper and AUR helper written in go.
Querying remotely is fine, also software updating. Folder exists but is empty.
ls /var/lib/pacman/local/|grep python-setuptools
python-setuptools-1:63.4.1-1
ls -a /var/lib/pacman/local/python-setuptools-1:63.4.1-1
. ..
Other subfolders at /var/lib/pacman/local/
contain desc file.
@hey951753 you can use yay like that if you want. i tend to use yay for aur packages only these days. but when i started with aur helpers years ago i used it for everything. it's a matter of what works best for your workflow
Are pacman wrappers like yay supposed to be used instead of pacman in every operation (e.g. installing packages from official repos, uninsralling packages), or just in AUR operations (installing packages from AUR)?
@saabzero, the question to you should really have been "is your system fully up to date"?
@callmejoe I have go 2:1.19-1 and gcc 12.2.0-1 installed using pacman
@saabzero do you have latest go and gcc versions installed?
to me compilation fails with:
/usr/lib/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/usr/bin/ld: /usr/lib/libc.so.6: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/libc.so.6 when searching for /usr/lib/libc.so.6
/usr/bin/ld: cannot find /usr/lib/libc.so.6
/usr/bin/ld: /usr/lib/libc.so.6: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/libc.so.6 when searching for /usr/lib/libc.so.6
/usr/bin/ld: /usr/lib/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/ld-linux-x86-64.so.2 when searching for /usr/lib/ld-linux-x86-64.so.2
/usr/bin/ld: cannot find /usr/lib/ld-linux-x86-64.so.2
/usr/bin/ld: /usr/lib/ld-linux-x86-64.so.2: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/ld-linux-x86-64.so.2 when searching for /usr/lib/ld-linux-x86-64.so.2
collect2: error: ld returned 1 exit status
Before writing that yay
doesn't work and that you are getting:
response decoding failed: invalid character '<' looking for beginning of value
Check these links:
yay -Syu yay ...
go: downloading golang.org/x/text v0.3.7
# runtime/cgo
In file included from /usr/include/errno.h:28,
from cgo-gcc-prolog:30:
/usr/include/bits/errno.h:26:11: фатальная ошибка: linux/errno.h: Нет такого файла или каталога
26 | # include <linux/errno.h>
| ^~~~~~~~~~~~~~~
компиляция прервана.
make: *** [Makefile:111: yay] Ошибка 2
==> ОШИБКА: Произошел сбой в build().
Прерывание...
-> ошибка сборки: yay
Pinned Comments
jguer commented on 2024-03-16 08:06 (UTC)
This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay
jguer commented on 2019-04-16 14:08 (UTC)
I cannot delete the spam comments appearing regularly in this page, which has also led me to disable notifications from here. I remind that the best way to receive support or report a problem is through the Upstream URL.