unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Ben Woodcroft <donttrustben@gmail.com>, guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Update pardre source hash.
Date: Thu, 08 Dec 2016 14:37:41 +0100	[thread overview]
Message-ID: <8760muzgm2.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161208131215.1205-1-donttrustben@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 781 bytes --]

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? Just checking
the substitutes ought to be sufficient. That said, I've seen this happen
in other distros, even at projects that "should know better" such as
Chromium, so I assume it was just a "quick and dirty" bugfix.

According to sourceforge it was updated July 6th, so it has likely been
garbage collected on Hydra.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2016-12-08 13:37 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 ` Marius Bakke [this message]
2016-12-08 14:17   ` [PATCH 0/1] Update pardre " Ricardo Wurmus
2016-12-08 14:19     ` Ricardo Wurmus
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=8760muzgm2.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=donttrustben@gmail.com \
    --cc=guix-devel@gnu.org \
    /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).