eva: bump revision and update checksum

[jcgruenhage]

Checksum changed since this was packaged. Does a revbump for stuff like this make sense? Probably not, right?

Upstream re-released v0.3.0, so the builds fail with bad checksum right now.

Testing the changes

• I tested the changes in this PR: YES

[classabbyamp]

did the contents of the tarball change?

[jcgruenhage]

I don't know whether the contents changed, I don't have an old checkout lying around...

[classabbyamp]

I don't know whether the contents changed, I don't have an old checkout lying around...

https://sources.voidlinux.org/eva-0.3.0/v0.3.0.tar.gz

[jcgruenhage]

Okay, yeah, the contents did change, and quite a bit. Reformatting, dependency updates, lots of new tests, functionality changes. This would mean we do also do a revbump here?

[tranzystorekk]

Maybe we could persuade upstream to make a proper new release number and just skip this?

[jcgruenhage]

That would just cause work for the maintainers of nixpkgs and Arch, who've already "dealt" with this by bumping a revision number though.

[tranzystorekk]

Ah, nevermind then, I was thinking maybe upstream have something on master branch worth a tiny patch bump, sth like that

[pickfire]

Sorry for the retag, but I can do a version bump if needed.

[tranzystorekk]

@pickfire I think as @jcgruenhage mentioned, a version bump would work if there are any meaningful changes left to be released, otherwise we just create churn for other distros, and I believe we can do a revision bump on our end for now