unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Update pardre source hash.
Date: Thu, 8 Dec 2016 15:19:43 +0100	[thread overview]
Message-ID: <idjmvg65wqo.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <idjoa0m5wuy.fsf@bimsb-sys02.mdc-berlin.net>


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...?

In fact, Leo informed me about this in July, but it seems that both of
us forgot to follow up on this.

Thanks, Ben, for catching it!

~~ Ricardo

  reply	other threads:[~2016-12-08 14:20 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 [this message]
2016-12-08 14:45     ` Marius Bakke
2016-12-10  1:08       ` Ben Woodcroft

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=idjmvg65wqo.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).