Re: [PATCH 0/1] Update pardre source hash.

[Ben Woodcroft <b.woodcroft@uq.edu.au>]

On 09/12/16 00:45, Marius Bakke wrote:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> Marius Bakke <mbakke@fastmail.com> writes:
>>
>>> Ben Woodcroft <donttrustben@gmail.com> writes:
>>>
>>>> Hi,
>>>>
>>>> It seems that the pardre source has been updated in place.  I'm not sure what
>>>> the procedure is for verifying that nothing untoward has taken place, since I
>>>> cannot download and old version from the hydra content addressed mirror -
>>>> it does not seem to exist there either.
>>> "diffoscope" has native support for tarballs and can quickly point out
>>> any differences. Perhaps Ricardo has a copy at the MDC?
>> I do!  I still have a copy of
>> /gnu/store/xp2yzil11yk9askvpp56a8jjqynqb12k-ParDRe-rel1.1.5.tar.gz
>>
>> The diff looks very familiar.  Could it be that this has happened
>> before?  Or maybe I noticed the changed hash before and forgot to submit
>> an update...?}
>>
>> [..]
> Looks like a portability fix, although I can't really tell what that
> bitshifting is about. Assuming it's the same as the GCC builtin :-)

Seems harmless enough, thanks you two.

I pushed an update to the hash to master, updating the version to 
"1.1.5-1" to reflect the fact that a change has been made, 
'7922ab8fe87154f3ccaa7daf9304632f974fbe5d'.

Is it possible to exclude sources from the GC on hydra or more 
importantly the new build system, for this reason?

ben