the issue is that when the new release 1.0.0 was added to the release section in github, @gkbrk create a package for ArchLinux for 1.0.0 and uploaded it to the repository https://aur.archlinux.org/packages/notes/. but just after that, I have made some changes in the code source and then I removed the version release 1.0.0 you have added and made a new one having the same version. That's why md5sums-checksum reports that there is an error as the code source have been modified.
the md5sums that was provided to Arch repo is : 63e42d1b8337c2c3f3d4a53754938b3b
but to be sure that there was no corruption in the package, the package manager check against source=($pkgname-$pkgver.tar.gz::"https://github.com/nuttyartist/notes/archive/v$pkgver.tar.gz")
So when the release 1.0.0 was changed the two md5sums are not equal anymore --> error.
so to handle this issue, @gkbrk should provide a new md5sums and regenerate a new package based on the new release 1.0.0 present in the release section in github.
great! So I will put the trusty for in the UPDATES.json file. Yet now what is the reason for us to put versions other than 14.04 on our site if they all going to update to 14.04?
Since I'm going to sleep now I will publish everything tomorrow which is a still good of a day (traffic wise).