Sometime the maintainers of packages from AUR are just on holiday or sick and the pkgbuild needs to be updated because the sources it uses have been updated but not the validity checksums of the pkgbuild.

The normal procedure would be to get into contact with the developer or flag it out of date on the AUR website and then the waiting starts. Or you can try to fix the pkgbuild yourself.

But what if that is all to cumbersome for you and you just want to have it NOW. It installed fine yesterday and does not install anymore today.

How to bypass these checksums if you know the packages are safe to install?

Yay

Trizen

You can make an alias for both of them.

We are going to add both aliases to our .bashrc in future releases.
You can always create as much aliases as you want.

how to fix the pkgbuild
2 solutions

1. Calculate and put in the correct sha256sum

2. Erase all trace of this html file

3th Solution 
how to fix the pkgbuild

3. Skip the sha256 checksum altogether

and big thank you to Musikolo, the maintainer of this package, for the quick response and the quick fix. He/she came up with the idea first to SKIP the whole checksum.