bug#34047: gnu: emacs-closql: Hash mismatch.

[Jelle Licht]

Oleg Pykhalov <address@hidden> writes: 

> [...]  HEAD is now at 012b94f Release version 1.0.0 r:sha256 
> hash mismatch for 
> /gnu/store/vy3m2n81i2ncpf65fnsq513dkwypzvr5-emacs-closql-1.0.0-checkout: 
>   expected hash: 
>   0cy44d1fxkvah6fhjkn3mp6gzzrjmws1c4c20ayrma74y9xich3v actual 
>   hash:   1xhpfjjkjqfc1k2rj77cscclz5r7gpvv3hi202x178vdcpipjwar 
> hash mismatch for store item 
> '/gnu/store/vy3m2n81i2ncpf65fnsq513dkwypzvr5-emacs-closql-1.0.0-checkout' 
> build of 
> /gnu/store/vrjbbp4n0kda1b7y98szwpv3n0pxm7nk-emacs-closql-1.0.0-checkout.drv 
> failed View build log at 
> '/var/log/guix/drvs/vr/jbbp4n0kda1b7y98szwpv3n0pxm7nk-emacs-closql-1.0.0-checkout.drv.bz2'. 
> killing process 14669 cannot build derivation 
> `/gnu/store/ykn80wrvznp2fp069yj9v7lnys7vqv6r-emacs-closql-1.0.0.drv': 
> 1 dependencies couldn't be built guix build: error: build 
> failed: build of 
> `/gnu/store/ykn80wrvznp2fp069yj9v7lnys7vqv6r-emacs-closql-1.0.0.drv' 
> failed 

You are totally right, my bad. Thanks for catching this!  Fixed in 
b03131902e2618de10d6be15531ca2b44717d397 on master.   For the 
interested, a snippet from IRC explaining my mistake: 
--8<---------------cut here---------------start------------->8--- 
2019-01-15 21:55 <jlicht> It _probably_ had something to do with 
the fact 
                         that I was messing around with several 
                         versions of emacs-closql before settling 
                         on the final one, but not updating the 
                         hash
2019-01-15 21:55 <jlicht> (which then worked because of the fun 
and 
                         interesting ways in which 
                         already-downloaded sources are 
                         referenced, I guess?) 

[...] 

2019-01-15 21:55 <civodul> jlicht: i see!
2019-01-15 21:56 <civodul> jlicht: it'd be nice to check the diff 
and explain 
                          in the commit log next time, just to be 
                          on the safe side!
2019-01-15 21:56 <jlicht> anyway, I took some time to verify that that new
                         hash is the actual one we want, using some vpn's
                         and some contact with coworkers. My apologies for
                         any bad dreams it may have given people
--8<---------------cut here---------------end--------------->8---

Thanks again Oleg for being so attentive.