Yay: skip failing packages

[moham96]

Affected Version

yay v9.4.2.r17.gb08e505b3422 - libalpm v12.0.1

Issue

When running an upgrade with yay -Su and one of the packages to be upgraded(or one of it's dependencies) fails to build, yay will quit and halt the whole upgrade process once it reaches the failing package.
it would be nice to have a flag to be used to tell yay to skip failing packages(if it's a dependency then don't bother building other dependencies of the package and skip it all together)
This would be very useful in scripts and auto-upgrade cronjobs

[LofhJann]

Partial upgrade is not supported by Arch Linux, hence shouldn't be supported by yay in my opinion. Surely you could do partial upgrade by not installing failing packages, but in reality you should never do it.

https://wiki.archlinux.org/index.php/System_maintenance#Partial_upgrades_are_unsupported

[Morganamilo]

Partial upgrades don't really apply to AUR packages.

[moham96]

I agree with @Morganamilo, Since most AUR packages are built locally they will be linked to whatever libraries present on the system and it will not cause breakage.

[Evanlec]

+1 please implement this feature for AUR packages. I agree of course about repo packages, one should upgrade all or nothing for those.

I have an ever-increasing list of AUR packages in need of upgrade (20+) and it's very difficult to upgrade them all because inevitably one of them fails to build, stopping the entire show.

When this happens, it makes 0 progress as not even a single package gets upgraded, even if I use the --nobatchinstall flag, it will _build_ the packages one by one, but it's _Not_ installing them directly after building (even though the documentation states that it should).

Thus when one package fails, nothing has been upgraded, and my only option is to upgrade them manually one at a time which is a gigantic PITA.

[C0D3D3V]

Would be cool if yay would automatically restart with the package that failed as --ignore parameter.

[neumannjan]

+1 agree with @Morganamilo . AUR packages are rarely dependent on each other, also the stability of your system rarely depends on AUR packages (because if it does, then you probably have to deal with much bigger update issues than just with missing partial update functionality). However, AUR packages do often fail to build and this halting updates for the rest of your packages makes no sense.

Therefore, I disagree with @LofhJann . Case in point: I doubt that the tonelib-jam-bin package failing to build will affect my google-chrome package in any negative way. :wink: