unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: parouby <contact@parouby.fr>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 32856@debbugs.gnu.org
Subject: [bug#32856] [PATCH] gnu: grammalecte: Update source hash.
Date: Fri, 28 Sep 2018 09:04:12 +0200	[thread overview]
Message-ID: <fbb6900d-80be-c4f9-0201-6b041ebab6ce@parouby.fr> (raw)
In-Reply-To: <87tvmahhig.fsf@tobias.gr>

Hi,

On 27/09/2018 21:23, Tobias Geerinckx-Rice wrote:
> This is a bit too... intriguing :-) IMO we should always explain what 
> changed & (when possible) why.
> 
> Were the exact same files recompressed with a non-deterministic 
> compressor? Did someone fix a typo hoping that nobody'd notice? 
> 'diffoscope' is a great tool for such questions (and it's in Guix).

I have no idea of who has change, I'm not developer on Grammalecte, just
user. When I when try to update my guix profile I have see the
Grammalecte package doesn't work.

I see the sha256 has change, but the zip file seems doesn't has been
modified. I thinks the modification date of zip has doesn't change.

---------------------------------------------------------------------
$ wget "http://www.dicollecte.org/grammalecte/zip/Grammalecte-fr-v0.6.5.zip"

$ ls -l
3122063 juil.  7 18:03 Grammalecte-fr-v0.6.5.zip
---------------------------------------------------------------------

There have been recent modification in guix hash ?

Br,
Pierre-Antoine Rouby

      parent reply	other threads:[~2018-09-28  7:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 19:01 [bug#32856] [PATCH] gnu: grammalecte: Update source hash Pierre-Antoine Rouby
2018-09-27 19:23 ` Tobias Geerinckx-Rice
2018-09-27 19:34   ` Tobias Geerinckx-Rice
2018-09-30 20:12     ` Ludovic Courtès
2018-10-02 21:05       ` bug#32856: " Ludovic Courtès
2018-10-02 21:23         ` [bug#32856] " Tobias Geerinckx-Rice
2018-09-28  7:04   ` parouby [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

  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=fbb6900d-80be-c4f9-0201-6b041ebab6ce@parouby.fr \
    --to=contact@parouby.fr \
    --cc=32856@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).