Updates of Cosmo versions will cause checksums to fail on dirty AUR package builds

[nicholatian]

When a new release is made and a user updates their installation with existing sources from an earlier makepkg run, and the version of Cosmo has been bumped, the fetcher script that does that will fail as checksums have changed but the old Cosmo sources remain. This happens because the Slick repo provides its own script for getting the Cosmo sources, instead of the AUR package() function fetching them itself. A dirty build will have the previous version of Cosmo sources already downloaded, and the script will not re-download them as they are non-trivial in size.

This is being filed for reference purposes here as a wontfix. Just clean build the package if the issue arises.