From: ludo@gnu.org (Ludovic Courtès)
To: Kei Kebreau <kkebreau@posteo.net>
Cc: 30436@debbugs.gnu.org, Amirouche Boubekki <amirouche@hypermove.net>
Subject: bug#30436: bigloo@4.3b hash mismatch
Date: Fri, 16 Feb 2018 09:59:58 +0100 [thread overview]
Message-ID: <87zi49s41d.fsf@gnu.org> (raw)
In-Reply-To: <87606xoeq3.fsf@posteo.net> (Kei Kebreau's message of "Thu, 15 Feb 2018 21:22:44 -0500")
Hello Kei,
Kei Kebreau <kkebreau@posteo.net> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> The original tarball should be available at:
>>
>> https://mirror.hydra.gnu.org/file/bigloo4.3b.tar.gz/sha256/1xpzxjlq5g8j3jrb908kfaaa0pkynk4rd083hzvb08amhy68sx07
>>
>> … but it’s not.
>>
>> Kei, could you check if you still have the tarball with this hash and
>> how it differs from the current one?
>>
>> Unfortunately Bigloo’s maintainer tends to overwrite files in place so
>> it’s likely that the file was modified after Kei committed the upgrade.
>>
>> Thanks,
>> Ludo’.
>
> I do have the "original" tarball, but I don't know how I can transfer it
> to you for inspection (if that is even necessary). However, I have
> attached changelog differences between the two source trees. I'd send
> the full diffoscope report, but its size is about 127 megabytes! The
> difference seems to be a string of miscellaneous fixes and changes.
Yeah, that’s what I expected. :-/ Thanks for checking.
Could you update the hash to the current hash in the ‘bigloo’ package
definition? Please add “Fixes <https://bugs.gnu.org/30436>.” to the
commit log so people can later see why we changed the hash.
Thank you!
Ludo’.
next prev parent reply other threads:[~2018-02-16 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 16:43 bug#30436: bigloo@4.3b hash mismatch Amirouche Boubekki
2018-02-12 16:59 ` Leo Famulari
2018-02-12 17:28 ` Amirouche Boubekki
2018-02-14 14:12 ` Ludovic Courtès
2018-02-16 2:22 ` Kei Kebreau
2018-02-16 8:59 ` Ludovic Courtès [this message]
2018-02-16 19:50 ` Kei Kebreau
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=87zi49s41d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30436@debbugs.gnu.org \
--cc=amirouche@hypermove.net \
--cc=kkebreau@posteo.net \
/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).