Failed to update AUR package

I’m trying to update from 4.4.165…

I guess it went trough using:

[jesuslinux@A9410 ~]$ yay -S --mflags --skipchecksums stremio

Don’t you see anything inherently wrong with skipping the validity check?

A better approach might be to find which file is failing, obtain its checksum value from the source, and update the PKGBUILD if everything seems in order.

I don’t know how to do that…

My point is that if whatever file is somehow damaged, and if that’s the reason for the validity check failing, the package might still continue to build by skipping the check, but might also cause you grief later.

This is just something for consideration.

In fairness, it might also be that the checksum simply hasn’t been updated in the PKGBUILD file and that the source is actually fine; in which case, see the the post from @cscs .


It seems to be working fine.
If it stops working I uninstall the AUR version and install the flatpak one.

It seems AUR is having some issues lately…

I don’t think the issue are caused by AUR as a source.

AUR should not be used by anyone on stable branch - using custom scripts from AUR assumes you are on Manjaro edge (unstable) branch.

There is a topic elaborating on the topic - search need to know about manjaro and aur

I usually recommend to build custom packages from the command line

sudo pacman-mirrors -aS unstable
git clone
cd streamio

if there is issues with the checksum (that may happen if the author bumps the release but forget to update checksums) run


continue with

makepkg -iscC

Works without issue for me when using makepkg.

Provided all the dependencies are there (installed from normal repo, nothing from AUR).

My procedure:
(get the snapshot from the AUR website.)

unpack it in its own directory
cd into that directory
run updpkgsums
then run makepkg

successful build without errors of: stremio-4.4.168-1-x86_64.pkg.tar.zst
found in the same directory
makepkg -i would have installed it after successful build

I just installed it using yay. No errors/warnings/problems whatsoever. Are you sure you did a clean build? or delete the cache.

The package has been updated to generate checksums for the git tag supported by pacman 6.1.0. Either switch to the testing branch or skip the checksums for now.

I believe that is what I did…

Is it working?
I’m confused.
I choose to go with: it’s working for you now.
Good! :+1:

You believe you did what? :thinking:

What branch are you using?

pacman-mirrors -G

What version of pacman do you have installed?

pacman -Qi pacman
[jesuslinux@A9410 ~]$ pacman-mirrors -G
[jesuslinux@A9410 ~]$ pacman -Qi pacman
Name            : pacman
Version         : 6.0.2-18
Description     : A library-based package manager with dependency support
Architecture    : x86_64
URL             :
Licenses        : GPL-2.0-or-later
Groups          : None
Provides        :
Depends On      : bash  glibc  libarchive  curl  gpgme  pacman-mirrorlist  gettext  gawk  coreutils  gnupg  grep
Optional Deps   : perl-locale-gettext: translation support in makepkg-template
Required By     : archlinux-keyring  base  base-devel  libpamac  manjaro-keyring  mhwd  pacman-contrib  yay
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 4,73 MiB
Packager        : Mark Wagie <>
Build Date      : sáb 10 fev 2024 15:51:23
Install Date    : sáb 24 fev 2024 21:19:32
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

It’s working fine just like before…

Now I’m even more confused
because to me

and the thread title
“Failed to update …”

look like contradictions.

I’ll leave this be.

It failed to update because of checksums error

No, it failed because…

…and you’re still using…

…which does not support it.

It failed to update - but now it does not fail anymore?
Is it that hard to communicate clearly?

Me and others did build it successfully.

I’ll shut up now.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.