From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Marius Bakke <mbakke@fastmail.com>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Update pardre source hash.
Date: Sat, 10 Dec 2016 11:08:27 +1000 [thread overview]
Message-ID: <74c28b0a-e3e3-1a71-310d-34ce9a90a7bf@uq.edu.au> (raw)
In-Reply-To: <87wpfaxyw8.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
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
prev parent reply other threads:[~2016-12-10 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 13:12 [PATCH 0/1] Update pardre source hash Ben Woodcroft
2016-12-08 13:12 ` [PATCH] gnu: pardre: Update " Ben Woodcroft
2016-12-08 13:37 ` [PATCH 0/1] Update pardre " Marius Bakke
2016-12-08 14:17 ` Ricardo Wurmus
2016-12-08 14:19 ` Ricardo Wurmus
2016-12-08 14:45 ` Marius Bakke
2016-12-10 1:08 ` Ben Woodcroft [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74c28b0a-e3e3-1a71-310d-34ce9a90a7bf@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.