signal: killed during yay runs

dvdesolve commented 3 years ago

Affected Version

$ yay -V
yay v10.3.1 - libalpm v13.0.0

Previous versions are affected as well

Describe the bug

During run of yay -Syu when it checks AUR packages sometimes I observer the following errors in stdout:

$ yay -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 apocalypse is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
:: Checking development packages...
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 there is nothing to do

A bunch of signal: killed floods my console screen. It happens from time to time, I can't find any specific pattern or so. It also exists on different machines with different CPUs, DEs, kernels etc

Reproduction Steps

Run yay -Syu, wait when it will check AUR packages
Observe lines with signal: killed

Expected behavior

No signal: killed will be shown

Output

$ yay -Pg
{
        "aururl": "https://aur.archlinux.org",
        "buildDir": "/home/viktor/.cache/yay",
        "absdir": "/home/viktor/.cache/yay/abs",
        "editor": "",
        "editorflags": "",
        "makepkgbin": "makepkg",
        "makepkgconf": "",
        "pacmanbin": "pacman",
        "pacmanconf": "/etc/pacman.conf",
        "redownload": "no",
        "rebuild": "no",
        "answerclean": "",
        "answerdiff": "",
        "answeredit": "",
        "answerupgrade": "",
        "gitbin": "git",
        "gpgbin": "gpg",
        "gpgflags": "",
        "mflags": "",
        "sortby": "votes",
        "searchby": "name-desc",
        "gitflags": "",
        "removemake": "yes",
        "sudobin": "sudo",
        "sudoflags": "",
        "requestsplitn": 150,
        "sortmode": 0,
        "completionrefreshtime": 7,
        "sudoloop": false,
        "timeupdate": false,
        "devel": true,
        "cleanAfter": false,
        "provides": true,
        "pgpfetch": true,
        "upgrademenu": true,
        "cleanmenu": true,
        "diffmenu": false,
        "editmenu": false,
        "combinedupgrade": false,
        "useask": false,
        "batchinstall": false
}

Jguer commented 3 years ago

Hey @dvdesolve , try yay-git it has some changes to Checking development packages mechanism.

This error comes from the git ls-remote used to check dev updates, normally it's due to some issue with your .gitconfig/ network/ a package that has gone private

BlackDex commented 2 years ago

for me this also happened, and i apparently had:

[core]
    rebase = false

In there, after i removed it, i suddenly got some packages which needed updating. While one fails building but i do not think this has something to do with yay.

dvdesolve commented 2 years ago

Haven't seen this bug for quite a long time. I think it was already fixed in upstream

Fabian42 commented 2 years ago

It happened to me on Sunday. yay version 11.0.2.

drujd commented 2 years ago

Happened to me 1 min ago. yay v11.0.2 - libalpm v13.0.1

:: Searching databases for updates... :: Searching AUR for updates... :: Checking development packages... -> signal: killed -> terminus-font-ll2-td1-ttf: local (4.49.1-1) is newer than AUR (4.48-1) -> Orphaned AUR Packages: terminus-font-ll2-td1-ttf there is nothing to do

Scotty-Trees commented 2 years ago

Can confirm, happening to me as well on EndeavourOS Gnome, using yay v11.0.2 - libalpm v13.0.1 First time I'm coming across this issue/error, btw.

Edit: I do have yay -Y --gendb and yay -Y --devel --save enabled if that's helpful also.

[scott@endeavourOS ~]$ yay
[sudo] password for scott: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 endeavouros is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
:: Checking development packages...
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> Flagged Out Of Date AUR Packages:  minecraft-launcher
 there is nothing to do

Here's all my AUR packages if it's helpful at all to know as well:

[scott@endeavourOS ~]$ pacman -Qm
archlinux-appstream-data-pamac 1:20211122-1
chrome-gnome-shell 10.1-5
gdm-prime 41.0+r15+g23ebe617-1
gwe 0.15.4-1
humanity-icon-theme 0.6.15-1
libgdm-prime 41.0+r15+g23ebe617-1
libpamac-aur 11.2.0-0
minecraft-launcher 928-1
nvm 0.39.1-1
optimus-manager 1.4-3
optimus-manager-qt 1.6.4-1
pamac-aur 10.3.0-1
papirus-folders 1.11.0-1
pika-backup 0.3.5-1
pop-gtk-theme-git 5.4.4.r13.g23d7ac83-1
popsicle-git 1.3.0.r47.gb02ebf5-1
python-hsaudiotag3k 1.1.3.post1-3
python-injector 0.19.0-1
python-isounidecode 0.3-3
python-pulsectl 1:21.10.5-1
python-py3nvml 0.2.7-1
python-pylyrics 1.1.0-2
python-pypresence 4.2.1-1
python-pysdl2 0.9.9-1
python-stagger 1.0.1-6
rhythmbox-plugin-alternative-toolbar 0.20.1-1
tauon-music-box 6.8.3-2
timeshift 21.09.1-3
ttf-ms-fonts 2.0-12
ttf-roboto-slab 3:2.001-1
wike 1.6.3-1
yaru-colors-gtk-theme-git 21.04.r6.gdbcbbff1-1
yaru-gnome-shell-theme-git 1:21.10.1.r258.gb369574d5-1
yaru-gtk-theme-git 1:21.10.1.r258.gb369574d5-1
yaru-gtksourceview-theme-git 1:21.10.1.r258.gb369574d5-1
yaru-icon-theme-git 1:21.10.1.r258.gb369574d5-1
yaru-metacity-theme-git 1:21.10.1.r258.gb369574d5-1
yaru-session-git 1:21.10.1.r258.gb369574d5-1
yaru-sound-theme-git 1:21.10.1.r258.gb369574d5-1
yaru-unity-theme-git 1:21.10.1.r258.gb369574d5-1
[scott@endeavourOS ~]$

Jguer commented 2 years ago

This is normally not a functional issue, just that yay failed to check one or more development packages. If you ran --gendb and the issue didn't go away (this would cover the url of the source having changed), it might be some setting of .gitconfig (for example: replacing https with ssh can sometimes have weird effects)

Scotty-Trees commented 2 years ago

This is normally not a functional issue, just that yay failed to check one or more development packages. If you ran --gendb and the issue didn't go away (this would cover the url of the source having changed), it might be some setting of .gitconfig (for example: replacing https with ssh can sometimes have weird effects)

I haven't done anything, and the message as magically gone away, so I just want to say sorry to have bothered you. I do love using yay btw :)

Fabian42 commented 2 years ago

I'm pretty sure this is network related. My internet connection just died while I was running yay and got this line 71 times.

ThatOneCalculator commented 2 years ago

--devel was working for me for a while and suddenly stopped working today. Any idea what I could do to solve it?

grandchild commented 2 years ago

and suddenly stopped working today

If you want help you have to be more detailed about how it stopped working. Terminal output, settings etc.

ThatOneCalculator commented 2 years ago

and suddenly stopped working today

If you want help you have to be more detailed about how it stopped working. Terminal output, settings etc.

Only output is signal: killed while running yay -Syu --devel

jonas-w commented 2 years ago

I get this error when running just yay and it pops up after "Checking development packages".

My config:

{
    "aururl": "https://aur.archlinux.org",
    "buildDir": "/home/jonas/.cache/yay",
    "editor": "",
    "editorflags": "",
    "makepkgbin": "makepkg",
    "makepkgconf": "",
    "pacmanbin": "pacman",
    "pacmanconf": "/etc/pacman.conf",
    "redownload": "no",
    "rebuild": "no",
    "answerclean": "",
    "answerdiff": "",
    "answeredit": "",
    "answerupgrade": "",
    "gitbin": "git",
    "gpgbin": "gpg",
    "gpgflags": "",
    "mflags": "",
    "sortby": "votes",
    "searchby": "name-desc",
    "gitflags": "",
    "removemake": "ask",
    "sudobin": "sudo",
    "sudoflags": "",
    "requestsplitn": 150,
    "completionrefreshtime": 7,
    "bottomup": true,
    "sudoloop": false,
    "timeupdate": false,
    "devel": true,
    "cleanAfter": false,
    "provides": true,
    "pgpfetch": true,
    "upgrademenu": true,
    "cleanmenu": true,
    "diffmenu": true,
    "editmenu": false,
    "combinedupgrade": true,
    "useask": false,
    "batchinstall": true,
    "singlelineresults": false,
    "separatesources": true,
    "version": "11.2.0"
}

JustSimplyKyle commented 1 year ago

This happened when I'm running yay -Y --gendb

:: (230/230) Parsing SRCINFO: looking-glass
 -> Found git repo: github.com/dszryan/pacmanity.git
 -> Found git repo: github.com/lbonn/rofi.git
 -> Found git repo: github.com/taganaka/SpeedTest.git
 -> Found git repo: github.com/HomeOfVapourSynthEvolution/VapourSynth-BM3D.git
 -> Found git repo: github.com/ypingcn/BingWallpaper.git
 -> Found git repo: github.com/hyprwm/Hyprland.git
 -> Found git repo: github.com/olive-editor/olive.git
 -> Found git repo: github.com/helix-editor/helix.git
 -> Found git repo: github.com/ytdl-org/youtube-dl.git
 -> Found git repo: git.sr.ht/~shinyzenith/wayout
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed
:: GenDB finished. No packages were installed

yay -Pg

{
    "aururl": "https://aur.archlinux.org",
    "buildDir": "/home/kyle/.cache/yay",
    "editor": "",
    "editorflags": "",
    "makepkgbin": "makepkg",
    "makepkgconf": "",
    "pacmanbin": "pacman",
    "pacmanconf": "/etc/pacman.conf",
    "redownload": "no",
    "rebuild": "no",
    "answerclean": "",
    "answerdiff": "",
    "answeredit": "",
    "answerupgrade": "",
    "gitbin": "git",
    "gpgbin": "gpg",
    "gpgflags": "",
    "mflags": "",
    "sortby": "votes",
    "searchby": "name-desc",
    "gitflags": "",
    "removemake": "ask",
    "sudobin": "sudo",
    "sudoflags": "",
    "requestsplitn": 150,
    "completionrefreshtime": 7,
    "maxconcurrentdownloads": 0,
    "bottomup": true,
    "sudoloop": false,
    "timeupdate": false,
    "devel": true,
    "cleanAfter": false,
    "provides": false,
    "pgpfetch": true,
    "upgrademenu": true,
    "cleanmenu": true,
    "diffmenu": true,
    "editmenu": false,
    "combinedupgrade": false,
    "useask": false,
    "batchinstall": false,
    "singlelineresults": false,
    "separatesources": true,
    "version": "11.3.0"
}

.gitconfig

[credential "https://github.com"]
    helper = !/usr/bin/gh auth git-credential
[user]
    email = private.com
    name = JustSimplyKyle
[core]
    editor = hx
[safe]
    directory = /usr/share/rime-data/iridium-bpmf
    directory = /opt/flutter

christophgysin commented 1 year ago

Happened to me while behind a VPN. I guess some git hosting services block my VPN provider's endpoint IP.

Jguer / yay