Arch Linux

jhf2442

Member

Registered: 2010-09-29

Posts: 17

[solved] yay failing on AUR package updates with bash error

Hi,

recently yay has started to fail when updating AUR packages :
after some time, following error message appears
/usr/bin/bash: warning: shell level (1000) too high, resetting to 1

updating packages from the regular repositories with yay just works fine

google tells that this message means that bash spawned 1000 childs

issue currently happens with brave-bin and betterbird-bin packages

only conscious modifications I did on my system was to merge several packnew files, some of them related to pacman
I was however not able to find any relevant change regarding this, but I have no version management on my /etc

is this problem somehow know, or could somebody give me a pointer how to debug / where to look at ?

Many thanks

Last edited by jhf2442 (2024-07-27 15:19:09)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,532

Website

Re: [solved] yay failing on AUR package updates with bash error

Mod note: not a pacman issue, moving to AUR Issues.

---

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.

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,330

Website

Re: [solved] yay failing on AUR package updates with bash error

Test with makepkg to determine whether the problem is the PKGBUILD(s) or yay.  The problem almost always is yay whenever possible (and sometimes when it shouldn't be), but I have a hunch here.

And before you try building with makepkg, read the PKGBUILD (you've been doing this already, of course, right?)

---

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

jhf2442

Member

Registered: 2010-09-29

Posts: 17

Re: [solved] yay failing on AUR package updates with bash error

Thanks for the pointer !
I have had a superficial look at the PKGBUILDs for brave-bin and betterbird-bin, assuming that there would be sufficient amount of users for both packages, and that an issue in them would be reported online in the AUR page

Running plain makepkg yielded in the same problem

Looking at the changes of my /etc/makepkg.conf vs the original provided in the packman package, I could spot several changes I made last week. One of which being https://wiki.archlinux.org/title/Makepk … _in_memory
which states:

The BUILDDIR variable can be temporarily exported to makepkg to set the build directory to an existing tmpfs. For example:

$ BUILDDIR=/tmp/makepkg makepkg

guess what I have put into my makepkg.conf .... feeling soooo stupid !

Problem solved :-(